Workspaces: personal and organization
Every account starts with a personal workspace. Organizations add seats, roles and shared billing. Here is how the two differ and when to use each.
Updated August 1, 2026
What a workspace is
A workspace is the thing that owns everything you create: API keys, credits, the plan, usage history and invoices. Your account signs in; your workspace holds the assets and pays the bills.
Every account gets one personal workspace automatically. You never have to create it, and it cannot be deleted while the account exists.
Personal vs organization
| Personal | Organization | |
|---|---|---|
| Created | automatically, one per account | you create it |
| Members | just you | many, with roles |
| Billing | your card, your credits | shared across the org |
| Plans | personal plans | organization plans |
| Seats | not applicable | capped by the plan |
An organization workspace exists when more than one person needs the same keys, credits and invoices. Billing is shared: a request made by any member spends the organization's credits, not the member's own.
An organization must be subscribed before it does anything
A new organization starts pending. In that state it has no credit allowance, its API keys will not authenticate, and members cannot be invited. Subscribing to an organization plan activates it — that one action sets the seat cap, the monthly credit allowance, the rate limit and the key limit together.
This is deliberate rather than a limitation. An organization is a billing entity, and an unsubscribed one has nobody to charge.
Switching between workspaces
The workspace switcher sits at the top of the dashboard. What you are looking at — keys, credits, usage — always belongs to the workspace currently selected, and it is worth checking before you spend.
Work in an organization workspace is charged to that organization. If you are a member of one, a request you make there draws on shared credits that someone else is paying for.
Roles
Members hold a role, and the role decides what they may do:
- Owner — everything, including billing and deleting the organization. There is exactly one.
- Admin — members, keys and settings, but not billing.
- Billing — plans, credits and invoices, but not keys or members.
- Developer — creates and revokes API keys, sees usage.
- Viewer — read-only.
Roles are per workspace. The same person can be an owner of their own organization and a viewer in someone else's.
Seats
Every plan has a seat cap. A seat is used by a member or by a pending invitation — an invitation that has not been accepted still holds the seat, because otherwise you could invite past the cap and let the acceptances race.
Moving to a plan with fewer seats than you have members is refused rather than silently truncated. Nobody should discover which colleague was removed on their behalf.
Related
Members, invitations and seats
How to invite people to an organization, what each role can do, how seats are counted, and what happens when an invitation expires.
Scheduled automation
Run a tool, a model, or both on a schedule — and have the result emailed, POSTed to your server, or saved.
AI tools: what they are and how they differ
A handful of our tools call an AI model instead of running in your browser. That changes three things: where your data goes, what a call costs, and whether you need an account.
Credits: the three pools and the order they are spent
Your balance is made of up to three different kinds of credit, and they are not spent in the order you might expect. This explains all three.