Settings and organization
Members and roles
Invite members with a role, change roles, remove members, transfer ownership, handle access requests, and rename, leave or delete an organization.
Roles belong to the organization and apply to all of its projects; there are no project-level roles. Manage them under Settings → Organization → Members in the sidebar footer.
Roles
| Action | Owner | Admin | Member | Viewer |
|---|---|---|---|---|
| Read the organization's data | yes | yes | yes | yes |
| Create projects and Environments | yes | yes | yes | yes |
| Manage members, invites, Providers and organization settings, and rename or delete projects | yes | yes | no | no |
| Edit an object (evaluator, Model, alert, queue, Environment and so on) | any | any | only ones they created | no |
| Grant the Owner role, by invite or on a member | yes | no | no | no |
| Grant Admin or Member | yes | yes | no | no |
| Read and decide access requests (API only) | yes | yes | no | no |
| Transfer ownership (API only) | yes | no | no | no |
| Delete the organization | yes | no | no | no |
Platform admins pass every membership check except organization deletion, which needs an Owner or a platform super admin. Your own role decides which controls the Members page shows. Its role menus offer Member, Admin and Owner; Viewer is given only through the API or an access request.
Invite, change, remove
Invite member takes an email and a role and sends a link that expires in 7 days. The invitee accepts by opening it signed in with the invited address; signed in as someone else, the page offers Switch account. A new user who registers through the link joins this organization and gets no personal workspace.
Resend gives a pending invite a fresh expiry, and Revoke makes its link stop working.
The role dropdown on a member's row changes the role, and demoting the last Owner is refused. Remove ends the member's access to the organization's projects at once; their runs and labels stay attributed to them. The founding owner cannot be removed.
Transfer ownership is API only: an Owner calls POST /orgs/:orgId/transfer-ownership. It makes the other member an Owner first and then makes you an Admin, so the organization never has zero Owners.
Access requests
Access requests are API only. In the app, a link into an organization you do not belong to offers only Choose a workspace.
A signed-in non-member sends POST /orgs/:orgId/access-requests with an optional message and requestedRole (Viewer by default); asking twice returns the pending request. Owners and Admins are notified, list requests with GET on the same path, and decide with POST .../:requestId/approve or .../deny. An Admin cannot approve a request for Owner, and no email tells the requester the outcome.
Rename, leave, delete
The organization's General tab renames it; the switcher, breadcrumbs and invite emails use the new name. Leave removes your own membership. The last Owner cannot leave and must transfer ownership first.
Only an Owner sees Delete organization. It deletes the projects even when they hold data, deactivates every Environment, and removes all memberships and the organization. It does not clean up project contents: datasets, runs, evaluators, collections and Providers stay in storage.