Skip to content

Administration ​

Features organization admins use for permissions, subscriptions, organization structure, auditing, and integrations. For the setup steps right after rollout, see the Admin Setup Guide.

Permission Management (RBAC: Role-Based Access Control) ​

EM-OS defines three roles to ensure access control based on the principle of least privilege:

  • Org Admin (OA): Highest administrator within the organization. Full permissions for settings, invitations, and data.
  • Lead (Manager): Responsible for a team. Can manage members, conduct 1on1s, approve ADRs, perform evaluations, and approve skill updates.
  • Member (General User): Standard access. Can update their own profile, participate in 1on1s, and view data (excluding private settings).

Who can do what in each feature, and the exceptions, are listed in What Each Role Can Do.

Subscription Management ​

Manage plan settings and payment information.

  • Plan Selection: Choose from Starter, Pro, and Enterprise. For the features and user limits of each plan, see Plans and Features.
  • Billing Integration (Stripe): Securely manage credit cards, view billing history, and upgrade plans via Stripe integration.
  • When the contract ends: Once there is neither an active plan nor a trial, administrators are taken to the subscription screen after signing in, and other members see the "access expired" screen. Subscribing again restores access.

Man-hour Analysis (Aggregation) ​

Analyze working hours and costs across the organization, teams, or projects.

  • Cost Visualization: Automatically aggregate estimated labor costs based on member unit rates (with configurable visibility).
  • Allocation Variance: Compare planned assignment ratios with actual entries from Work Logs to verify resource allocation.

Organizational Design (Topology) ​

Define the organization's structure from a "Team Topologies" perspective.

  • Team Types: Assign types (Stream-aligned, Enabling, Platform, Complicated Subsystem) to each team.
  • Interaction Patterns: Define how teams work together (Collaboration, X-as-a-Service, Facilitating) to optimize communication.

Audit Logs ​

Record "who did what and when" for all operations to support security audits.

Key Log Targets ​

  • Authentication: Logins, logouts, and failed attempts.
  • Organization: Team creation/deletion, role changes, and invitation issuance.
  • Management: Subscription plan changes and system setting updates.
  • Data: Deletion of ADRs and operations on sensitive artifacts.

CSV Export ​

Use the "Export" button on the Audit Logs screen to download audit logs as a CSV file.

  • Scope: Every log matching the current filters (action, period, etc.) is exported, not just the page currently shown.
  • Limit: Up to 10,000 logs per export. If more logs match, the newest 10,000 are exported and you are notified. Narrow the period or other filters and export in several batches.
  • Recording: The export itself is also recorded in the audit logs.

External Integrations ​

For setup steps, see Connect External Tools.

Connect external services to EM-OS to automatically collect and sync data.

Supported Providers ​

  • GitHub:
    • Features: Sync Four Keys metrics, issues, and user profiles.
  • Slack:
    • Features: Alert notifications, approval flow notifications (Skill updates, ADRs, etc.), and analysis of communication between teams.
  • Google Calendar:
    • Features: Scheduling 1on1s.
  • AWS (beta) and GCP:
    • Features: Importing infrastructure monitoring metrics and checking SLO (Stability) achievement.
  • Jira:
    • Setup: Register an Atlassian API token, your Jira domain (xxx.atlassian.net), and the email address of your Atlassian account.
    • Features: Import and sync Jira projects and tickets. When creating a project on the Projects screen, choose "Jira" as the import source to search for and import Jira projects and tickets.
    • Sync: Imported projects store the Jira project key (e.g. PROJ) in "Project Number", and the sync button on the Projects screen brings in the latest state from Jira. To sync a project you created manually, enter the Jira project key in "Project Number" on its edit screen.

Financial Visibility Settings ​

Decide which roles in your organization can see monetary values such as unit rates and costs on the "Allocation" screen.

  • Only organization admins (ADMIN) can change it, using the "Financial Visibility Settings" switch on the "Allocation" screen.
  • The setting is stored per organization and does not affect other organizations.
  • By default the amounts are shown to admins only. With "Visible to Leads", team leads also see the amounts for the teams they manage.
  • Changes are recorded in the audit log.

Onboarding Flow ​

New users complete an initial setup (onboarding) on their first sign-in. The screens depend on their role.

  • Members and leads: Account Settings → Skill Self-Check → Ready
  • Organization admins: Account Settings → Org Profile Settings → Team Topology Configuration → Ready

Admins assign teams when they invite members. For the invitation steps, see Invite Members.

Invitations and Joining ​

  • Signing in with Google / GitHub from an invitation link joins the invited organization even if the email domain differs from the organization's.
  • If you are already signed in, open the invitation link and select "Join with this account". If you are signed in with a different account than the invited one, you are asked to sign out and sign in with the invited account.
  • Without an invitation link, only people who sign in with an email on a domain registered and verified for the organization can join it during onboarding (Verify ownership of the domain).
  • Archived members cannot rejoin unless invited. An archived member who signs in again with the same email is rejected. To bring them back, send a new invitation. A member archived while signed in sees the "account deleted" screen on their next action.
  • When the organization has reached the user limit of its plan, joining through an invitation is rejected too.

Integrated platform for engineering management · Terms · Privacy