Workspaces
Workspaces are containers within an organization that group related projects and control who can access them.
What a workspace is
Section titled “What a workspace is”A workspace lives inside an organization and provides:
- A boundary for grouping related projects (e.g. by team, engagement, or client)
- Fine-grained access control via user and team permissions
- A unique
key(URL slug) within the organization
Each user gets a default workspace that is private to them. Additional workspaces can be created and shared with other members.
Permissions
Section titled “Permissions”Workspace access is controlled separately from organization roles. Permissions can be granted to individual users or to teams.
| Permission | What it allows |
|---|---|
| Owner | Full access — manage permissions, delete |
| Contributor | Create and manage projects within workspace |
| Reader | View projects and traces |
User permissions
Section titled “User permissions”Individual users can be added to a workspace with a specific permission level. The workspace creator is automatically assigned the owner permission.
Team permissions
Section titled “Team permissions”Teams (groups of users within the organization) can also be granted workspace access. All members of the team inherit the team’s permission level for that workspace.
Default workspaces
Section titled “Default workspaces”When a user joins an organization, they receive a default workspace that is private to them. Default workspaces:
- Are automatically created and cannot be deleted
- Are not shared with other members unless explicitly configured
- Provide a personal space for individual projects
Managing workspaces
Section titled “Managing workspaces”- API: Create a workspace with
POST /api/v1/org/{org}/ws. Retrieve details withGET /api/v1/org/{org}/ws/{workspace}. - Sharing: Add users with
POST /api/v1/org/{org}/ws/{workspace}/users. - Listing: All workspaces in an organization are listed at
GET /api/v1/org/{org}/ws.