# Organizations and workspaces

How Tokenlane groups people, credit and keys: the organization holds members and money, workspaces separate projects.

## Organization

The organization owns the credit balance, top-ups, billing details and the member list. Every workspace and key belongs to exactly one organization. Switching organization switches the whole context; the balance does not move with you. You can select only organizations in which you are currently a member, and after signing in again Tokenlane restores your last selection.

Roles: **owner** manages the organization including credit and owners. **Admin** manages all workspaces, settings, keys and members, but only owners manage owners. **Member** uses the assigned workspaces with the rights granted there. People join by email invitation.

Owners and admins open **Manage organization** in the organization menu to set the name, logo, a two-factor requirement for all members (API keys and gateway requests are unaffected), automatic membership of new members in the default workspace and balance notifications. The logo (PNG, JPEG, WebP or simple SVG, up to 2 MiB) is shown to members only.

## Workspace

A workspace groups the keys, activity and logs of a project, team or environment. Each key belongs to one workspace, and the views show one workspace or **All workspaces**. A workspace has no separate prepaid balance: its keys are charged to the organization's shared credit. An optional workspace budget limits their combined spending, including concurrent reservations.

Workspaces have members with their own roles. A **viewer** reads the overview, Activity and Logs without captured contents. A **developer** also manages their own keys. A **workspace admin** manages all keys, settings and members. Owners and admins of the organization reach every workspace. Each organization starts with a default workspace, which new members join as developers while automatic membership is on.

The directory counts organization owners and admins with implicit access plus explicitly assigned workspace members. Owners and admins create workspaces from the workspace menu or the Workspaces page. A management key can read workspaces but not create them.

## Where credit, people and rules live

| | Organization | Workspace | Key |
| --- | --- | --- | --- |
| Credit | Balance, top-ups, invoices | None, charged to the organization | Optional limit in EUR |
| People | Owner, admin, member | Viewer, developer, workspace admin | Attributed to a member or the workspace |
| Rules | Model, provider and privacy restrictions | Inherited restrictions and shared spending budget | Inherited rules plus key restrictions |

Organization, workspace and key policies are intersected, so a lower level or request can only narrow access. A workspace budget that cannot cover an estimated reservation returns `402 workspace_budget_exceeded`; organization credit and key limits remain separate. Expiry, positive `capture` and server-tool grants belong to the key, while inherited `forbid_capture` can prohibit content storage. See [Authentication](https://tokenlane.de/docs/guides/authentication.md?lang=en) and [Privacy and compliance](https://tokenlane.de/docs/guides/privacy-and-compliance.md?lang=en).

## Next

- [Quickstart](https://tokenlane.de/docs/guides/quickstart.md?lang=en): create a key in the right workspace
- [Costs and limits](https://tokenlane.de/docs/guides/costs-and-limits.md?lang=en): how the shared credit is spent