Skip to main content
Account setup covers everything between signing up and having everyone tracked: your organization, its teams, its members, each engineer’s machine, and how Terma ties identities to people.

​
Your organization

When you first sign up, Terma creates an organization for you and asks you to Name your organization. Everything else lives inside it: teams, members, the GitHub connection, and principal mapping. You can belong to several organizations. Switch between them with the organization switcher in the top bar, or create another with New organization. On the command line, terma setup --org <name> switches the organization your machine reports to.

​
Teams

A team is where activity lands. Every session, usage figure, and attributed commit belongs to one team. Use separate teams to separate products, groups of people, or anything you want to report on separately.
  • Create a team from your organization’s home page with New team. Terma opens a setup guide for connecting your first tools.
  • Choose what the team collects on Team settings → Data collection. An organization admin sets the team’s policy: every session, or only the repositories it lists, and whether commits are stamped and prompts and tool content are sent. See Settings.
  • Delete a team from its Team settings page. Only organization admins can delete teams.
Each engineer chooses their team when they run terma setup, and every session they run reports to that team. If your organization has only one team, it is chosen for them. To switch, run terma setup --team <name>.

​
Members and roles

Invite colleagues from Settings → Organization (or during onboarding). Enter their email addresses and select Send invite. Invited people join as members and don’t need a beta invite code. Pending invitations can be resent or revoked. To delete an organization, select Request deletion in its settings; deletion is handled by Terma support.

​
Onboarding each engineer

Nothing is committed to your repositories, so each engineer sets up their own machine once:
terma setup signs them in, asks which agents they use and which team they’re on, and configures their agents machine-wide. They restart any running agents, then run terma doctor to check everything works. See Installation and terma setup.
Sessions are collected only where the team’s policy allows. If the policy lists repositories, make sure each repository engineers work in is on the list. terma doctor shows the origin terma sees and whether the team collects it.

​
Identities and principal mapping

Sources report identities, not people. The same engineer may be ada@example.com to Claude Code, a different user id to Codex, and an API key to OpenRouter. Each identity is a principal. Organization admins map principals to members on Team settings → Principals: seat each identity to the member it belongs to, or give it an alias. Identities seated to one person roll up as that person across every metric, in every team. The Overview shows a banner when a team has unmapped principals.

​
Keys

Claude Code and Codex need no keys: terma setup handles sign-in and routing. A machine with no one to sign in, such as a CI runner or an ephemeral VM, is the exception: it signs in with an Ingest only key (Headless setup). For other tools, such as OpenRouter, Team settings → API keys lists the team’s keys. Revoke one there when a tool no longer needs it. See Settings.