Workspaces

Create independent workspaces, switch context, and understand dynamic workspace authorization.

Workspaces

Every account has a default Personal Workspace. Existing resources that used the user’s stable account ID remain available through a compatibility layer, while newly created workspaces use generated ws_... identifiers.

Create and list workspaces

curl -X POST \
  -H "Authorization: Bearer $QUANTURA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"Institutional Research","description":"Forecast datasets and research exports"}' \
  https://quantura.studio/api/v1/workspaces

curl -H "Authorization: Bearer $QUANTURA_API_KEY" \
  https://quantura.studio/api/v1/workspaces

Use the returned stable id in CSV and other workspace-specific routes. Names and slugs may change and must not be treated as authorization identifiers.

Workspace roles apply only inside the shared workspace. A user who is a Viewer in another person’s workspace retains normal permissions in their own workspace.

Role	Read authorized resources	Create or modify	Manage workspace access
Owner	Yes	Yes	Yes
Admin	Yes	Broad, within explicit capabilities	Yes, except owner-only actions
Editor	Yes	Rename, copy, and move when permitted	No by default
Analyst	Yes	Upload/create when permitted	No
Viewer	Yes	No	No

Viewer collaborators can use a personal API key to read resources explicitly shared through the workspace even when their personal plan does not grant unrelated standalone API compute.

Dynamic enforcement

Tokens do not permanently encode workspace privileges. Every request checks the current membership and role. Removing a collaborator immediately removes access for that token on its next request.

Use GET /api/v1/me/access to inspect effective workspace access without returning any credentials.

See Workspace collaboration for the complete permission vocabulary, resource-specific scope, and collaborator lifecycle.