Workspaces and members
A workspace is the unit everything belongs to: notebooks, files, environments, experiment runs, runtimes, storage connections, transfers and secrets. You get a personal workspace when your account is created, and you can create more from the workspace switcher at the top of the sidebar.
Your workspaces
- New workspace in the switcher creates one with the name you give it; the switcher also renames the current one (Rename Workspace).
- An account may own up to 10 live workspaces. Deleting one frees its slot.
- One storage pool per account. Every workspace you own draws on the same 250 GB pool. A workspace somebody else owns draws on their pool, not yours; the Files page says so when you are working in one.
- One running runtime per workspace. Opening a second notebook attaches to the runtime that is already running.
Roles
Every member has one role. Roles are ranked, so an editor can do everything a viewer can, and the owner can do everything an editor can.
| Role | What it can do |
|---|---|
| Viewer | Read everything in the workspace: notebooks, files, runs, environments, connection and transfer lists, secret names. Open a running runtime's web ports. Keep their own experiment dashboard and private saved views. Every write is refused. |
| Editor | Everything that changes the workspace: create and edit notebooks and files, launch, stop and restart runtimes, use the terminal and SSH, build environments, add connections and run transfers, manage secrets, share objects and create public links, save shared experiment views, rename the workspace. |
| Owner | Everything above, plus invite and remove members and delete the workspace. The owner is the account that created the workspace. |
A run can be deleted by the member who created it or by the workspace owner. Membership is the only way to write into a workspace: a share grant gives view and copy access to one object, never a role (see Sharing).
Members
Settings, Members lists everyone in the current workspace. The owner can:
- Invite by email. The person must already have a Neural Studio account; they are added immediately as Editor or Viewer, with no invitation to accept.
- Remove a member. They lose access at their next request, their SSH key is removed from the workspace's running runtimes, and a runtime they could reach is stopped ("Stopped because a member was removed from the workspace"). To change someone's role, remove them and invite them again with the new role.
Members see the workspace in their own switcher and can open everything their role allows. They are never charged for what the workspace holds: storage counts against the owner's pool, and a runtime is paid for by the member who started it.
Deleting a workspace
Settings, Delete workspace is owner-only and cannot be undone. The confirmation shows what goes with it:
- every notebook, file and run in the workspace;
- environments created in the workspace, images included (a build in progress is cancelled);
- access for every member.
Billing records stay with your account. The delete is refused while a runtime in the workspace is live, or while a runtime elsewhere is using one of the workspace's environments: stop it first. Once the workspace is gone, its slot is free and its files' space returns to your pool.
Related
- Your account and billing: the subscription, credits and the storage pool.
- Sharing: giving one person or anyone with a link access to a single object without adding them to the workspace.
- Limits: the workspace and storage numbers.