> ## 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.

# Inviting Team Members

> Bring your team into Alethia and assign the right roles.

You don't have to use Alethia alone. Invite teammates, give them roles, and collaborate on testing — every action is attributed to a specific person, so there's no confusion about who did what.

## Before you invite

Decide two things first:

<CardGroup cols={2}>
  <Card title="Which team?" icon="users">
    The person joins a specific team within your organization. They'll have access to that team's projects, prompt library, and LLM configurations.
  </Card>

  <Card title="Which role?" icon="user-tag">
    Pick from Team Admin, Tester, or Viewer. See [Roles](/essentials/hierarchy#team-roles) for what each one can do.
  </Card>
</CardGroup>

## Sending an invite

<Steps>
  <Step title="Open Members">
    Either:

    * **Organization → Members** (you must be an Org Owner or Admin) — invites someone to any team in the org.
    * **Team → Members** (you must be a Team Admin) — invites someone specifically to your team.
  </Step>

  <Step title="Click 'Invite Member'">
    The invite form opens.
  </Step>

  <Step title="Enter their email">
    Use their work email when possible.
  </Step>

  <Step title="Pick the team and role">
    The role determines what they can do once they join. You can change it later.
  </Step>

  <Step title="Send">
    They get an email with a unique invite link, valid for **7 days**.
  </Step>
</Steps>

## What the recipient sees

When they click the invite link:

* **If they already have an Alethia account:** they log in and are added to the team immediately.
* **If they're new:** they go through registration, and the moment they finish, they're auto-joined to the team with the role you assigned.

Either way, they land in the team and can start working right away.

## Managing pending invites

In the **Members** page, you'll see two lists:

* **Active members** — already in the team
* **Pending invites** — sent but not yet accepted

For pending invites you can:

* **Resend** — sends the invite email again (useful if the original was missed)
* **Revoke** — invalidates the link

## Changing someone's role

<Steps>
  <Step>Go to **Team → Members**.</Step>
  <Step>Find the person and click the role dropdown next to their name.</Step>
  <Step>Pick the new role. The change takes effect immediately.</Step>
</Steps>

## Removing someone

<Steps>
  <Step>From **Team → Members**, click the **⋯** menu next to the person.</Step>
  <Step>Click **Remove from team**.</Step>
  <Step>Confirm.</Step>
</Steps>

The user keeps their Alethia account but loses access to your team's projects, prompts, and LLM configurations. Anything they created (test runs, risk entries, etc.) stays — attribution is preserved.

<Warning>
  **Removing someone doesn't delete their work.** All their test runs, risk entries, mitigations, and overrides remain in place, attributed to their account. The audit trail is preserved.
</Warning>

## Inviting many people at once

If you're rolling Alethia out to a larger team, invite them in batches:

<Steps>
  <Step>From the Members page, click **Bulk Invite**.</Step>
  <Step>Paste a list of emails (one per line, or comma-separated).</Step>
  <Step>Pick the team and a default role for everyone in the batch.</Step>
  <Step>Send. Each person gets an individual invite email.</Step>
</Steps>

## Cross-team membership

A single user can be a member of **multiple teams**, with potentially different roles in each. For example:

* Team Admin in *Production*
* Tester in *Research*
* Viewer in *Compliance*

They'll see a team switcher at the top of the sidebar to jump between teams.

## Best practices

<Tip>
  **Default new joiners to Tester.** Start most people with Tester role. Promote to Team Admin only for people who need to manage members or approve risk classifications.
</Tip>

<Tip>
  **Use Viewer for stakeholders.** Compliance officers, executives, and external auditors typically only need read access. Viewer keeps them from accidentally changing things.
</Tip>

<Tip>
  **Audit the member list quarterly.** Roll off members who've left. The audit trail keeps their past actions; removing them just stops future access.
</Tip>