Organizations & Workspaces
Invite teammates, set roles, switch workspaces and keep billing separate per organization.
An organization gives a team one shared workspace: shared API keys, one credit pool, presets, logs and BYOK credentials, gated by roles. Solo users should stay in their personal workspace.
Every account has one private personal workspace (created on first sign-in) and can belong to any number of organizations, with a different role in each. The workspace picker in the dashboard sidebar switches between them and decides what you see.
Roles
Each member has one role per organization, and every organization keeps at least one owner.
| Capability | Owner | Admin | Member |
|---|---|---|---|
| View keys, credits balance, logs and usage | Yes | Yes | Yes |
| Create and revoke API keys | Yes | Yes | No |
| Create and edit shared presets | Yes | Yes | No |
| Store and rotate BYOK credentials | Yes | Yes | No |
| Invite, remove members, change roles | Yes | Yes | No |
| Top up credits or change billing | Yes | No | No |
| Promote to owner, transfer ownership, delete the organization | Yes | No | No |
Members can make requests, browse presets and view logs and credits.
Workspace-scoped vs. account-scoped
| Workspace-scoped (changes with the picker) | Account-scoped |
|---|---|
API keys (sk-ar-...), BYOK credentials, presets (@preset/<slug> can resolve differently per workspace), credits, usage and logs | Profile, authentication (session, MFA, recovery), notification preferences |
Requests are authenticated by the key, not the picker. A personal key always charges your personal credits; an organization key always charges that organization.
Billing
- Credits are held per workspace. Only an owner can top up or change billing; receipts go to that owner and are visible to owners and admins.
- Any request with an organization key draws from the organization's pool; members need no credits of their own.
- There is no per-seat charge. Seat pricing may come to Enterprise plans.
- Owners and admins can opt in to low-balance email alerts.
Invite teammates
- Open the organization on the Organizations page and click Invite member.
- Enter the email, pick Admin or Member, and send.
The invitee gets a sign-in link; the organization appears in their picker once they accept (after creating an account if needed). Invitations expire after 7 days; resending refreshes the expiry, and you can revoke a pending invitation before acceptance. After acceptance, remove the member instead.
To leave, choose Leave organization on the Organizations page. Keys you created stay with the organization and keep working.
The last owner cannot leave or downgrade. Transfer ownership first, or delete the organization, which permanently removes every key, preset, log and credit balance with no recovery.
SSO and enterprise
Enterprise organizations can enable SAML SSO (Okta, Azure AD, Google Workspace and others); an owner configures it in organization settings. Once enforced, members can no longer use email or social sign-in for that organization.
- Domain verification. Verify your email domains with a DNS TXT record before enabling SSO.
- SCIM. Your IdP can create, update and deprovision members automatically; removing a user from the IdP removes them on the next sync.
Contact us through the dashboard support link to start.
FAQ
| Question | Answer |
|---|---|
| Move a key from personal to an organization? | No. Mint a new organization key and update your clients. |
| Do teammates see my personal-key requests? | No. Personal traffic never appears in organization logs. |
| What do members see of each other? | Display name, avatar and role only. |
| Delete my account while sole owner? | Blocked until you transfer ownership or delete the organization. |
| Rename an organization? | Owners and admins, from the Organizations page. |
AnyRouter routes requests to third-party models. Models and outputs are provided as is, with no warranty; you use them at your own risk. Disclaimer