Workspaces
A workspace is the top-level container for datasets, reports, dashboards, and sharing grants. Every asset in OneAnalytics belongs to exactly one workspace — assets never live at the tenant root.
Why workspaces
Workspaces solve three problems:
- Organisation — Finance, Sales, and Ops teams each get their own space; browsing stays focused.
- Access control — Permissions are granted into a workspace. A user with
editoron theFinanceworkspace sees nothing inSales. - Billing boundaries — Storage quota, refresh quota, and per-workspace feature flags can be applied independently.
Roles inside a workspace
| Role | Can read | Can edit | Can share | Can manage members |
|---|---|---|---|---|
| Viewer | yes | no | no | no |
| Editor | yes | yes | yes | no |
| Admin | yes | yes | yes | yes |
The tenant-wide Owner role always has Admin privileges in every workspace.
Creating a workspace
curl -X POST https://api.analytics.rstglobal.in/v1/workspaces \
-H "Authorization: Bearer $OA_TOKEN" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{"name": "Finance", "description": "GL, AP, AR, cash"}'
Response is a Workspace object with a UUID — keep it, you'll need it when creating datasets.
What belongs to a workspace
- Datasets (and their refresh schedules, semantic models, row-level security rules)
- Reports and dashboards (and their layouts, filters, bookmarks)
- Alerts (every alert is scoped to a dataset in the same workspace)
- Sharing grants (
subject_idmust resolve to an asset in the workspace) - Tags, folders, and saved queries
Moving assets
A dataset or report can be moved between workspaces by any Owner. Sharing grants on the moved asset are re-evaluated; any principal who loses access is notified by email.