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

# Teams and Members

> Create teams, invite members, manage roles, and switch between teams.

Onyx organizes everything by team: projects, campaigns, experiments, API keys, and GitHub connections are all team-scoped. You can belong to any number of teams and switch between them at any time.

## Switching and Creating Teams

The team dropdown in the breadcrumb at the top of the app switches your active team. It also includes:

* **Create new team** — opens a dialog, makes you the new team's admin, and switches to it right away.
* **Manage team** — jumps to the team's member settings.

## Roles

| Role   | Capabilities                                                          |
| ------ | --------------------------------------------------------------------- |
| Admin  | Manage team settings, members, invitations, licenses, data, and keys. |
| Editor | Read and write team research data; manage their own keys.             |
| Viewer | Read team research data; manage their own keys.                       |

Every team needs at least one admin: the last admin can't be demoted, removed, or leave. Delete the team instead if you're done with it.

## Inviting Members

Admins invite members from **Settings → Members** by email, choosing a role for the invitee. New users get an invitation email with a sign-up link. Invitees who already have an Onyx account don't get an email — the invitation appears as a banner in the app once they sign in with the invited email address. Either way, you can copy an invite link from the pending invitations table to share directly. Recipients can accept or decline. Pending invitations can be revoked at any time, and expire after 7 days.

## Managing Members

From **Settings → Members**, admins can change member roles or remove members. Removing a member (or leaving a team yourself) also revokes that member's API keys for the team, so CLI access ends together with app access.

## Team Settings

**Settings** uses a side navigation:

* **General** — rename the team, see its plan, and delete the team. Deleting a team permanently removes its projects, campaigns, experiments, API keys, GitHub connections, and invitations for every member.
* **Members** — invite, manage roles, remove members, leave the team.
* **API Keys** — manage team-scoped API access and CLI profiles.
* **Account** — your profile, as provided by your sign-in identity.
* **Integrations** — the team's GitHub connections.