Settings and organization

Members and roles

Invite members with a role, change roles, remove members, transfer ownership, handle access requests from non-members, rename or leave an organization.

After this page the member list reflects the team, each person has the role they need, stale invites are gone, and you know what each role may do.

Roles

Action	Owner	Admin	Member	Viewer
read the organization’s data	yes	yes	yes	yes
manage members, invites, Providers, organization settings; rename or delete projects; create, rotate, delete Environments	yes	yes	no	no
edit an object (evaluator, Model, alert, queue …)	any	any	only ones they created	no
invite as Owner or grant the Owner role	yes	no	no	no
grant Admin or Member	yes	yes	no	no
read and decide access requests	yes	yes	no	no
transfer ownership	yes	no	no	no
delete the organization	yes	no	no	no

Roles are organization-wide; there are no project-level roles. Members may create projects. Platform admins bypass membership checks except organization deletion. Your own role decides which controls the Members page shows.

Invite, change, remove

Organization settings → Members (sidebar footer → Settings → Organization → Members) lists members (name · email · role · joined) and pending invites. Invite member takes an email and a role and sends an email whose link opens a public preview (organization, role, inviter, whether it has expired); accepting requires signing in with the invited address, and a new user who registers through it lands in this organization with no personal sandbox. Pending invites can be resent (a fresh expiry) or revoked (the link stops working). The role dropdown on a row changes a role — demoting the last Owner is refused; Remove ends access on the member’s next request (their runs and labels stay attributed to them; the founding owner cannot be removed). Transfer ownership promotes another member to Owner first, then demotes you to Admin, so the organization never has zero owners.

Access requests

A signed-in non-member who opens a link into your organization sees You don’t have access and can Request access with a message. Owners and Admins get a notification and see the request on the Members page with Approve (adds the member with the requested role, Viewer by default; an Admin cannot approve a request for Owner) or Deny. One pending request per person; asking twice re-reports the first. The requester learns the outcome by reloading — no email is sent for a decision.

Rename, leave, delete

General renames the organization (switcher, breadcrumbs and invite emails use the new name). Leave organization removes your own membership — refused for the last Owner, who must transfer first. Delete organization is Owner-only and requires force when projects remain: it deactivates Environments, deletes projects and memberships and the organization itself; evaluators, collections, Providers, datasets and runs of the organization are not removed by that cascade.