Skip to main content
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:

Which team?

The person joins a specific team within your organization. They’ll have access to that team’s projects, prompt library, and LLM configurations.

Which role?

Pick from Team Admin, Tester, or Viewer. See Roles for what each one can do.

​
Sending an invite

1

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

Click 'Invite Member'

The invite form opens.
3

Enter their email

Use their work email when possible.
4

Pick the team and role

The role determines what they can do once they join. You can change it later.
5

Send

They get an email with a unique invite link, valid for 7 days.

​
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

1
Go to Team → Members.
2
Find the person and click the role dropdown next to their name.
3
Pick the new role. The change takes effect immediately.

​
Removing someone

1
From Team → Members, click the ⋯ menu next to the person.
2
Click Remove from team.
3
Confirm.
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.
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.

​
Inviting many people at once

If you’re rolling Alethia out to a larger team, invite them in batches:
1
From the Members page, click Bulk Invite.
2
Paste a list of emails (one per line, or comma-separated).
3
Pick the team and a default role for everyone in the batch.
4
Send. Each person gets an individual invite email.

​
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

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.
Use Viewer for stakeholders. Compliance officers, executives, and external auditors typically only need read access. Viewer keeps them from accidentally changing things.
Audit the member list quarterly. Roll off members who’ve left. The audit trail keeps their past actions; removing them just stops future access.