Organizations & People
Roles and AccessEnterprise
Account roles, dashboard roles and Portal access, and what each allows.
A person's access is made of an account role and, for each organization they belong to, a dashboard role, Portal access, or both. The account role covers the account itself; the dashboard role and Portal access cover one organization each. Together they decide where the person can sign in and what they can manage.
Account roles
The account role is the person's role in the account itself:
| Account role | Allows |
|---|---|
| Owner | Everything an admin can do. The owner created the account, and their account role stays Owner. |
| Admin | Managing the account's people on the Account Roster, creating organizations and tools policies, and account settings such as single sign-on, user provisioning and machine identity issuers. Working in the account's own resources. |
| Member | Working in the account's own resources, such as its routers and prompts. |
| No Operator Access | Dashboard access through named organizations only, or the Portal only. Used for people who work in named organizations, or only use the Portal. |
An account admin is an admin of the account in the access rule, and sees every person and organization in the account.
Dashboard roles
The dashboard role is the person's role in one named organization:
| Dashboard role | Allows |
|---|---|
| Admin | Everything a member can do, and managing the organization's people and their tools policies, budgets, webhook endpoints and GitHub connections, renaming and deleting the organization. |
| Member | Working in the organization's resources: routers, prompts, API keys, provider keys, model groups and Traffic. |
| None | Portal access only, when the person has it there. |
Portal access
Portal access lets a person set up tools such as Claude Code and Claude Desktop for themselves from the Portal, in one organization, under a tools policy that decides which tools and models they get. Portal access is separate from the dashboard role: a person can have either, both or neither in each organization. A person with only Portal access signs in to the Portal and is sent there from the dashboard. See Self-Service Provisioning.
Examples
Common combinations and what they give:
| Person | Account role | Organization access | Result |
|---|---|---|---|
| Platform lead | Admin | Admin in every organization | Manages everyone and everything. |
| Team lead | Member | Admin in Engineering | Manages Engineering's people and resources, and works in the account's resources. |
| Engineer | No Operator Access | Member in Engineering, with Portal access | Works in Engineering in the dashboard, and sets up Claude Code from the Portal. |
| Support agent | No Operator Access | Portal access in Support | Uses Claude Desktop set up from the Portal, and works only in the Portal. |
Protections
A few changes are reserved, so that the account always has someone who can manage it:
| Change | Rule |
|---|---|
| The account owner's account role | Stays Owner. |
| Suspending or offboarding the account owner | Reserved; the owner stays active. |
| Suspending or offboarding yourself | Another admin does it. |