Skip to main content
Version: 2026.8.1

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.

  • Park a workspace: set its plan to disabled. Reversible.
  • Remove a workspace: a hard delete, type the slug to confirm. No undo.
  • Answer "I cannot get in": look the account up in Users, then view-as.

The workspaces list​

Each row shows:

  • Name and slug.
  • Owner's email.
  • Member count.
  • Created.
  • Last activity: the quickest read on whether a workspace is live or abandoned.

Freeze a workspace​

Set the workspace's plan field to disabled.

  • 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 restores everything exactly as it was. Use it to park a workspace without losing anything.
  • free and paid exist for instances that bill. Self-hosted, they are equivalent, so disabled is the only value that matters.

Remove a workspace​

  1. Removing a workspace is a hard delete: it drops that workspace's own database and everything in it.
  2. 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:

  • Workspace memberships and the role it holds in each.
  • Email and display name.
  • The active flag.
  • Whether a password reset is pending.
  • Last login time.

The common use is a support question:

  1. Someone says they cannot get into a workspace.
  2. Look up which workspaces they belong to and with what role before deciding what to do.
  3. To 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.