Organization settings

Organization → Settings manages who belongs to your organization and what they can do. Your identity provider only authenticates users — membership here is what ties an authenticated identity to the organization and grants it anything.

Only org admins can change membership; everyone else sees the roster read-only.

Your organization ID

The screen shows the organization's ID with a copy action. You need it when authenticating the CLI (--org <org_id>) and for programmatic API access alongside an API token.

Inviting a member

Invite a user by email — it must match the email their identity provider asserts, because membership is keyed by email. Choose a role:

• Org admin — everything, org-wide.
• Org member — org access only; workspace grants determine what they can build.
• Workspace admin — manages one workspace; you pick the workspace as part of the invite.
• Developer — builds within one workspace; also workspace-scoped.

Workspace-scoped grants automatically make the user an org member. The invite takes effect the next time the user signs in — there is no email notification to accept.

Managing existing members

Each member row is read-only until you click its edit (pencil) action:

• Change the org role — switch a member between admin and member; save applies it immediately.
• Revoke workspace access — remove an individual workspace grant from the member without touching their org membership.
• Remove the member — removes them from the organization entirely; they can still authenticate with the identity provider but will land on the "no organization" screen.

How roles map to workspaces

Within a workspace, a member appears as either Workspace admin or Developer. Org admins are not listed per workspace — they implicitly have access to every workspace, including creating new ones. For how these roles shape day-to-day work, see Workspaces and environments.