Organization Workspaces
Invite teammates, assign roles, and control who can launch what — without sharing logins.
Workspaces, not shared passwords
One org holds the wallet. Members join a workspace. Each member has an org role: admin owns everything, member sees only what you grant.
- Org
admin— full control, all capabilities, delete org, buy seats. - Org
member— base access + granted capabilities + per-member caps.
Platform roles (user / staff / admin) are separate — a billing user can still be an org admin.
Invite flow
- Org admin opens Organization → Members → Invite.
- Enter email. Seat check runs first: 3 free seats, then $10/seat/month.
- Invitee accepts under Organization → Invitations (pending list).
- Admin assigns capabilities + caps after accept.
Duplicate pending invite or seat limit hit = invite rejected. Clear stale invites before retry.
Delegable capabilities
| Capability | Gates |
|---|---|
members:manage | Invite, revoke, update members, assign instance caps |
settings:manage | Org settings updates |
sshkeys:manage | Org SSH-key add/remove |
Org-admin-only (never delegable): delete org, purchase seats. Role changes gated to org admins — delegates cannot self-promote.
Per-member caps
Set by org admin, ignored for admins:
MaxInstances— instance count cap.AllowedTiers— launchable tiers (empty = all).DailyGPUHourLimit/WeeklyGPUHourLimit— consumption caps.
Hit member instance allocation exceeded or tier not allowed? Ask org admin to raise cap, not support.
Seats and billing
Seat purchase charges org wallet immediately. Watch balance before inviting for a deadline run. See Wallet and Top-ups and Pricing and Billing.