# Members and roles

Organization roles control broad capabilities. Domain permissions separately control which parts of an ontology an editor may change.

Admins manage members under **Organization → Users**.

## Choose a role

| Role | Access |
| --- | --- |
| Explorer | Ask questions and read the ontology |
| Editor | Explorer access, plus ontology 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 or use Google. 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](/setup/permissions/) for narrower edit rights and [API keys](/setup/api-keys/) for automation.