Team
Organizations
Shared workspaces for teams — one pool of machines, models, workflows, and billing.
An organization is a shared workspace: everything in it — machines, workflows, models, assets, credits — belongs to the team rather than any individual.
Creating an organization
- Open the workspace switcher (top-left) → Create organization
- Name it, invite members by email
- Switch between Personal and org workspaces any time from the same switcher — each has fully separate resources and billing
What's shared in an org
| Shared | Stays personal |
|---|---|
| Machines, workflows, models, assets | Your personal workspace's everything |
| Credit balance & plan | Personal credits |
| API keys created in the org | Personal API keys |
| Run history (Analytics shows who ran what) |
Seats & roles
Member limits come from your plan (seats sync automatically when your plan changes). Member permissions are covered in Roles — including the "User" role for people who should only use the Playground.
Billing note: in an org workspace, all GPU usage debits the org's credits, regardless of which member ran it. The Usage page and Analytics show the breakdown.