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

# Organizations, Teams & Roles

> How Alethia structures users, teams, and access permissions.

Alethia is built for teams — not just individuals. To make that work, the platform uses three layers of access:

```
Organization  (your company)
  └── Team    (a department or working group)
       └── Member  (an individual person)
```

## Organization

The **organization** is the top of the tree. It usually represents your whole company. There's one billing plan per organization, and one organization can hold multiple teams.

The person who creates the organization automatically becomes its **Owner**.

| Organization role | What they can do                                                                        |
| ----------------- | --------------------------------------------------------------------------------------- |
| **Owner**         | Everything — billing, deleting the org, creating/removing teams, transferring ownership |
| **Admin**         | Manage teams and members across the org. Cannot manage billing or delete the org.       |
| **Member**        | Sees the org exists, but needs to be added to a specific team to do anything useful     |

## Team

A **team** is a working group inside the organization. Maybe it represents a product line ("Customer Support AI"), a department ("Compliance"), or a specific client engagement.

Each team has its own:

* **Prompt Library** — the prompts available to all projects in the team
* **LLM Configurations** — the API keys and models the team can use
* **Projects** — the actual testing workspaces

Different teams can't see each other's data. A user can belong to multiple teams.

## Team roles

Once you're a member of a team, you have one of three roles:

| Team role      | Projects     | Prompts      | Run tests    | Override verdicts | API keys      | Manage members |
| -------------- | ------------ | ------------ | ------------ | ----------------- | ------------- | -------------- |
| **Team Admin** | Full control | Full control | Yes          | Yes               | Manage        | Yes            |
| **Tester**     | View, create | Full control | Yes          | Yes               | View (masked) | View only      |
| **Viewer**     | View only    | View only    | View results | No                | No access     | View only      |

<Tip>
  **Most users are Testers.** Day-to-day testing, prompt management, and verdict overrides all work in this role.

  **Viewer** is great for stakeholders, auditors, and execs who need read-only visibility without the risk of accidental changes.
</Tip>

## Project

A **project** is a focused workspace tied to **one specific model under test** (e.g., "GPT-4o", "Claude Sonnet 4", "Our fine-tuned LLaMA v3"). Test runs, schedules, and risk records all live inside the project.

Read more in [Projects](/essentials/projects).

## How permissions work in practice

Imagine **Acme Corp** has two teams: a *Research* team experimenting with frontier models, and a *Production* team gating what ships to customers.

* **Sara** is an Org Admin and Team Admin in both teams. She invites people, sets up API keys, and approves risk classifications.
* **Marco** is a Tester in *Production* only. He runs scheduled tests, reviews results, and overrides verdicts when needed.
* **Lin** is a Viewer in both teams. She sits in compliance — she can see every result and download every report, but cannot change anything.

This layered model means people only see what they need to see, and every change is attributable to a specific user.

## Inviting people

<Steps>
  <Step title="Open Members">
    Go to **Organization → Members** (Org Owners/Admins) or **Team → Members** (Team Admins).
  </Step>

  <Step title="Send an invite">
    Enter the person's email, pick the team, and choose their role.
  </Step>

  <Step title="They click the link">
    The invite email contains a unique link valid for 7 days.
  </Step>

  <Step title="They join automatically">
    If they already have an Alethia account, they're added immediately. If not, they'll register and join in one step.
  </Step>
</Steps>

See full instructions in [Invite Members](/account/invite-members).