Members and roles
Organization roles control broad capabilities. Domain permissions separately control which parts of the context an editor may change.
Admins manage members under Organization → Users.
Choose a role
| Role | Access |
|---|---|
| Explorer | Ask questions and read the context |
| Editor | Explorer access, plus context changes, evals, and issue triage |
| Admin | Editor access, plus projects, members, roles, and integrations |
Invite or change a member
- Invite
- Enter the email address and role. The link lasts seven days; pending invites can be resent after one hour.
- Sign in
- The teammate can set a password (at least 8 characters and at most 72 bytes, so fewer characters with accents or emoji) or use Google. Accepting the invite confirms the email address, so there is no separate confirmation email. Google sign-in needs an address Google reports as verified. An address already attached to another organization cannot be moved through an invite.
- Suspend
- Stops sign-in while preserving the account and history. Reactivate from the same page.
- Change role
- Takes effect immediately.
Admins can inspect organization conversations in the web app. MCP conversations remain visible only to their author.
Use Domain permissions for narrower edit rights and API keys for automation.