Skip to main content

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. That last column is the quickest read on whether a workspace is live or abandoned.

Freeze a workspace​

Each workspace carries a plan: free, paid, or disabled. Setting it to disabled is a real switch, not a label. While a workspace is disabled the api refuses every request scoped to it, so nobody can read or write its data. Login still works, and flipping it back to free or paid restores everything exactly as it was. Use it to park a workspace without losing anything.

Remove a workspace​

Removing a workspace is a hard delete. It drops that workspace's own database and everything in it. The console makes you type the slug to confirm, because there is no undo. This is for clearing out 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, with each account's workspace memberships and the role it holds in each. Alongside the email and display name you get 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.

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