Skip to main content
ChecklistWorkspacesOrganizations & teamsAdministration

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.

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

Download markdown

1Before you create anything

Decide the workspace boundary
One workspace per team, per project, or per environment? Storage and resource allocation follow this boundary, so it is easier to decide now than to move later.
Choose a plan against expected concurrency
Plan limits govern how many sessions and clusters can run at once, not only total capacity. A team of ten on a plan sized for two will queue.

2Set it up

Create the workspace and confirm it reaches a deployed state
Provisioning takes a few minutes. Wait for the dashboard to report the workspace as deployed before inviting anyone into it.
Invite members with the narrowest role that works
Roles govern what someone can change, not only what they can see. Start restrictive; widening later is easier than explaining a deleted workspace.
Verify persistent storage is where people expect
Confirm the intended storage location is mounted and writable, and tell the team which paths survive a session restart and which do not.

3Before handing it over

Install shared dependencies once
Anything the whole team needs should be installed in the workspace, not by each person in their own session.
Run one end-to-end job yourself
Launch a cluster, run a trivial distributed task, confirm it completes, then shut it down. Finding a problem now is cheaper than five people finding it separately.
Confirm activity logging is visible to whoever needs it
Check that the people accountable for the environment can see the activity trail before anything goes wrong rather than after.

More like this

All resources
Quick guideWorkspace admin

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.

4 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