Workspaces and users
Two tabs cover the roster of your instance: Workspaces lists every space, Users lists every account. Both are cross-workspace, which is the whole point of the operator tier.
The workspaces list
- Each row shows: the workspace name and slug, its owner's email, how many members it has, when it was created, and the last time anything happened in it.
- The last-activity column is the quickest read on whether a workspace is live or abandoned.
Freeze a workspace
Set the workspace's plan to disabled to park it without losing anything.
- Plans:
free,paid, ordisabled. - Disabled is a real switch, not a label: the api refuses every request scoped to that workspace, so nobody can read or write its data. Login still works.
- Flipping it back to
freeorpaidrestores everything exactly as it was.
Remove a workspace
- Removing is a hard delete: it drops that workspace's own database and everything in it.
- You type the slug to confirm, because there is no undo.
- Use it for a test space or one whose owner has left, not for a routine pause. To pause, disable it instead.
The users list
The Users tab shows every account on the instance, newest first.
- Each account shows: email and display name, its workspace memberships and the role it holds in each, the active flag, whether a password reset is pending, and the last login time.
- The common use is a support question: someone says they cannot get into a workspace, and you look up which workspaces they belong to and with what role before deciding what to do.
- To then see what they see, use view-as.
Related
- Instance-wide health numbers live on the Metrics page.
- Adding people to the instance is covered in Invites and signups.
- What a workspace is, and why each one keeps its own database, is in Workspaces.