Workspaces and Organizations
Workspaces separate API keys, backends, model groups, usage, and access control. Billing is attached to the workspace owner: either a personal account or an Organization.
Personal Workspaces
Every account has a personal Default Workspace.
- Free accounts can use the Default Workspace only.
- Paid personal accounts can create additional personal workspaces.
- Personal workspaces do not support invited members; they are owned by the account user.
- Extra personal workspaces are suspended if the owner downgrades to Free or loses the paid plan because of payment failure, expiration, or external cancellation.
Suspension is not deletion. The workspace data stays available for history and recovery, but configuration writes are blocked until the paid plan is restored.
Organization Workspaces
Organizations are for teams that need shared billing and shared access.
- Organizations require a paid Startup subscription.
- All Organization workspaces share the same Organization credits.
- Usage remains separated by workspace so owners can understand which product or team spent credits.
- Organization workspaces support members and invitations.
- Organization owners can create additional Organization workspaces.
Roles
Organization workspace members can have one of three roles:
| Role | Typical permissions |
|---|---|
| Owner | Manage workspace settings, billing recovery access, members, invitations, and owner-level actions. |
| Admin | Manage most workspace resources and invite admin/member users, but cannot grant or remove owner access. |
| Member | Use workspace resources according to the keys and access granted to them. |
Personal workspaces do not use team roles beyond the owner.
Suspended vs Archived
Suspended and archived workspaces have different meanings.
| State | Why it happens | User-visible effect |
|---|---|---|
| Suspended | Billing recovery state, such as a personal downgrade or an Organization payment failure that credits could not cover | Configuration changes are blocked. Existing active API keys can still run inference while the billing account has credits. |
| Archived | A workspace owner archives a non-default workspace | Active keys are revoked, inference stops for that workspace, non-owner members are removed, and the workspace is kept for history instead of being physically deleted. |
The Default Workspace cannot be archived.
Billing Impact
The most important rule is that credits are shared at the billing-account level.
- A personal paid account spends one personal credit balance across its personal workspaces.
- An Organization spends one Organization credit balance across all Organization workspaces.
- A suspended workspace does not by itself stop inference; credit balance and API key status decide whether inference can continue.
- An archived workspace does stop inference because its active keys are revoked.
For more detail on downgrade, payment failure, and top-up behavior, see Billing and Plans.