OrganizationsWorkspaces

Workspaces

A workspace is a sub-space inside a team organization. Workspaces let a team separate its API keys, usage, and spend into groups, for example one workspace per project, team, or environment (such as staging and production).

Every organization has a default workspace. Team organizations can add more; personal organizations always have exactly one workspace and cannot add others.

The active workspace

As with organizations, one workspace is active at a time inside a team organization, and it scopes what you see. On the analytics and activity dashboards you can switch between this workspace and all workspaces (the organization-wide rollup). The rollup view is available to the roles that can read organization-wide data: owner, admin, billing admin, and analyst.

Two scopes over the same data

This workspaceKeys, usage, request logs, budgets. What a developer sees.

All workspacesThe organization-wide rollup. Needs the finance read permission.

Most reads are scoped to the active workspace. The org-wide rollup is a separate, permission-gated view — which is why a developer sees their workspace's spend but not the organization's bill.

Managing workspaces

Go to Settings, then Workspaces. Depending on your role you can:

Create a workspace and name it. Requires an owner or admin.
Rename a workspace.
Archive a workspace you no longer use. The default workspace cannot be archived.

Archived workspaces are shown muted and offer no further actions. Creating and renaming require the workspaces permission; archiving requires the workspace-delete permission (owner or admin).

Previous← Members and roles NextAPI keys →