Browse the docs

Workspaces

One workspace per product or per client: creating, switching, renaming and archiving.

On this page
  1. The current workspace
  2. Create a workspace
  3. What is separate, and what is shared
  4. Rename
  5. Archive
  6. API

A workspace is the boundary around a set of pages, monitors, incidents and subscribers. Everything you do in the dashboard happens inside the current workspace, shown at the top of the sidebar. Most teams need one. Agencies need one per client.

The current workspace

The switcher under the logo shows the organisation and the workspace you are in. Every list on every screen is filtered to it. Switching does not sign you out; it changes what you are looking at.

Create a workspace

Workspace settings with the name field and the list of workspaces
Settings, Workspace: rename the current one or create another.

Settings, Workspace, then New workspace. Give it a name; the slug is generated. The new workspace starts empty: no pages, no monitors, no members other than the organisation-level ones who see everything.

Plans set how many workspaces an organisation can have: one on Free and Starter, three on Team, more on Enterprise.

What is separate, and what is shared

Per workspacePer organisation
Status pages, components, custom domainsPlan and billing
Incidents, maintenance windows, message templatesOrganisation-level members (owner, admin, billing)
Monitors and their checksAPI keys (bound to one workspace or organisation-wide)
SubscribersPlan limits: pages and monitors are counted across all workspaces
Outbound webhooks
Workspace-level members and roles
Audit log

Rename

Settings, Workspace. The name shows in the switcher and in the audit log. The slug does not change.

Archive

Archiving hides the workspace and everything in it. Its pages stop being served, its monitors stop checking, and it no longer counts against limits. The default workspace cannot be archived. There is no un-archive in the dashboard yet; contact support if you need one back.

For an agency, the pattern is one workspace per client, with the client's own staff invited as workspace-level members. They sign in and see only their workspace.

API

GET /user/workspaces lists the ones your credentials can see; POST /user/orgs/:orgId/workspaces creates; PATCH and DELETE /user/workspaces/:id rename and archive. See Workspaces in the API reference.