Skip to main content
Quick guideWorkspace adminWorkspacesOrganizations & teamsBilling & plans

Quick guide: workspace admin

Setup order, member roles, and the two numbers worth watching weekly: usage against plan limits, and clusters still running after their work finished.

0 of 4 checked(not saved, download a copy to keep)

Download markdown

1Setup order

Organization, then workspace, then members
The organization owns workspaces and is the unit of billing. Create the workspace and wait for it to reach a deployed state before inviting anyone.
Assign the narrowest role that works
Roles govern what a person can change, not only what they can see. Widening access later is easier than recovering a deleted workspace.

2What to watch

Usage against plan limits
Limits govern concurrency as well as capacity. This is the number that turns into a month-end surprise if nobody looks at it.
Clusters still running after jobs finish
An idle cluster bills like a busy one. It is the largest avoidable cost in most organizations.

More like this

All resources
Checklist

Workspace setup checklist

Stand up a workspace a team can actually work in, in the right order: storage and libraries before access, access before the first cluster.

8 items
Quick guideOrg owner

Quick guide: org owner

Plans, accountability, and the questions worth asking monthly: who is spending what, which limits are close, and whether access still matches the team.

4 items
Checklist

Cost optimization checklist

Keep compute spend predictable without giving up throughput: what to check weekly, how to stop paying for idle clusters, and where to right-size.

7 items