> ## Documentation Index
> Fetch the complete documentation index at: https://docs.terma.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Set Up Your Terma Account, Projects, and Team Access

> Create your Terma workspace, invite teammates, configure projects, manage organization settings, and get your team onboarded to the CLI.

Account setup covers everything between signing up and having your full team tracked: creating your workspace, structuring it into projects, getting engineers onboarded to the CLI, and understanding how Terma identifies the people behind your AI activity. Work through these sections in order the first time, or jump to a specific topic if you're returning to adjust an existing setup.

## Creating Your Account

Sign up for free at [https://dev.terma.ai/sign-up](https://dev.terma.ai/sign-up). You can authenticate using GitHub or Google OAuth, or register with an email address and password. No credit card is required at any point during signup.

After you authenticate, Terma provisions your workspace and creates a default project. You can rename the project, add repositories, and invite team members from the dashboard immediately after signing up.

## Projects

Projects are the primary organizational unit in Terma. Each project groups a set of repositories and the team members who work in them, and all usage reports, findings, and budget envelopes are scoped to a project.

To select which project the CLI reads from and writes to, run:

```bash theme={null}
terma project use <name>
```

The active project persists across CLI sessions until you change it. The dashboard always reflects activity scoped to the project you're currently viewing, matching the CLI selection.

Use separate projects to isolate distinct products, teams, or billing boundaries — for example, one project per engineering squad, or one per product line.

## Team Members

Engineers onboard individually. Each developer runs `terma setup` once on their own machine to sign in, bind their identity, and connect their local coding agents:

```bash theme={null}
terma setup
```

You only need to run `terma install` once per repository. Once that pull request is merged, every engineer who has completed `terma setup` is automatically covered — Terma matches their agent sessions to their identity through the credentials they established during setup.

There is no separate invitation flow to complete before an engineer can run `terma setup`. Share the [quickstart](/quickstart) with your team and ask each person to run through steps 3 and 4 on their own machine.

## Identity and Principals

Terma tracks activity through **principals** — named identities associated with a person. One engineer can appear as multiple principals if they use different tools or accounts: for example, the same person might be a Claude Code principal under one email and a Codex principal under another.

To resolve a name, email, alias, or ID to all the principals Terma associates with that person, run:

```bash theme={null}
terma principal find <name>
```

This is useful when reviewing usage reports and you want to confirm that all of a teammate's activity — across tools and providers — is being attributed correctly to a single person.

## Organizations

Organizations sit above projects and let you manage multiple teams or business units from one Terma account. To see every organization your credential belongs to, run:

```bash theme={null}
terma org list
```

Use organizations for multi-team setups where separate projects need to share billing, access controls, or consolidated reporting at the company level.

<Note>
  Traffic attributed to an API key rather than a named person shows as `(no user id)` in usage reports. Use `--group api-key` to identify which key is responsible for that spend and determine whether it needs to be tied to a principal.
</Note>