Workspace Setup
Workspace lifecycle management — creating, renaming, and deleting workspaces, and seeding demo workspaces for evaluation and training.
At a glance
| Route | /organization/workspaces |
| Group | Admin |
| Page permission | organization |
What it is
Workspace lifecycle management: creating, renaming, and deleting workspaces, and seeding demo workspaces for evaluation and training.
Who it is for
Organisation administrators structuring the tenancy.
How it works
A workspace is the platform's data boundary. Cloud connections, spend, findings, policies, and audit logs belong to exactly one.
Isolation is structural, not filtered
Data cannot leak across workspaces because queries are scoped structurally rather than filtered after the fact. This is what makes multi-entity, multi-business-unit, and partner-managed deployments safe.
Workspace count is plan-limited: one on Explorer, three on Pro, ten on Business, unlimited on Enterprise.
Demo seeding
Demo seeding populates a workspace with representative data — so the product can be evaluated, or a team trained, without connecting production clouds.
Features
- Workspace creation, renaming, and deletion
- Demo workspace seeding with representative data
- Plan-limited workspace counts, enforced server-side
- Clean environment lifecycle control
How to use it
Decide the workspace structure deliberately before creating any
Common patterns:
| Pattern | When it fits |
|---|---|
| One per business unit | Separate P&Ls, separate FinOps ownership |
| One per environment class | Strong prod/non-prod separation requirements |
| One per acquired entity | Distinct cloud estates not yet consolidated |
Create a demo workspace first and seed it
So evaluation and training happen against data that cannot be damaged.
Name workspaces to match how your organisation actually refers to those boundaries
Not how an architecture diagram labels them.
Delete demo workspaces once training is complete
So they do not distort organisation-level analytics.
Why it matters
The workspace boundary is what makes multi-entity, multi-business-unit, and partner-managed deployments safe.
And demo seeding removes the chicken-and-egg problem of evaluating a cost platform before trusting it with production credentials.
Connects to
- Bounded by plan limits in Membership
- Populated through Cloud Accounts
- Aggregated in Org Analytics
- Every module in the product is workspace-scoped