# 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.

Source: https://university.eugo.io/resources/workspace-setup-checklist

---

- Kind: Checklist
- Topics: workspaces, orgs-teams, administration

## Before 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.

## Set 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.

## Before 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.