Personal vs organization
When you sign up, you start in personal mode. Everything you create (sessions, secrets, API keys) belongs to you alone. When you create or join an organization, you can switch context. Resources you create while in an org context are owned by the org and visible to other members.Roles
Organization members have one of three roles:
Roles affect two things:
- What you can do in the dashboard - the UI hides actions you don’t have access to
- What scopes your API keys can carry - a member cannot create an API key with
templates:writeeven if they try. See Scopes for the full ceiling matrix.
Require organization workspace
Owners and admins can turn on Require organization workspace in Settings → Team. Members then can’t switch to Personal mode or create another organization from the dashboard. API and CLI calls can still use personal scope.Single sign-on
Owners and admins can connect Okta (OIDC) or Duo (SAML) in Settings → Team → Single sign-on:- Add the identity provider’s details. Each org can have one connection.
- Verify your email domain by adding the DNS TXT record Runtime shows you. A domain another org has already verified can’t be used.
- People sign in from the login page with Continue with SSO. New users get an account and existing users on the domain are linked. Both join your org as members, even when public signups are closed. Existing roles don’t change.
API keys and org context
API keys are bound to one context at creation time:- Personal keys operate as you without any organization. They can manage your sessions, personal secrets, and user instructions.
- Org keys operate as you within a specific organization. They can access org-scoped resources up to your role’s ceiling.
X-Organization-Id header interacts with API keys.