Skip to content
Browse documentation

Manage workspaces

Understand workspace selection, membership, owner actions, and invitations.

Markdown

Workspaces separate metrics, dashboards, alarms, notification channels, roles, and API tokens. Use them when different products, environments, teams, or customers need separate data and access control.

Most app pages operate inside the currently selected workspace. The selected workspace controls which metrics you see, which dashboards you edit, which roles are available, and where new API tokens are created.

Open the Workspaces page

Open Workspaces from the main menu.

The page lists every workspace available to your account. Each workspace card shows:

  • workspace name and ID;
  • whether it is the current workspace;
  • your effective role;
  • whether you are the owner or a member;
  • owner account ID;
  • creation and update times.

Select a workspace

Select Switch on a workspace card to make it the current workspace.

After switching, the app returns to the dashboard home page. Requests you make after that use the selected workspace, including metrics, dashboards, alarms, roles, and API tokens.

If your account has access to more than one workspace, switch before creating resources so they are created in the intended workspace.

Owners and members

Every workspace has one owner account. The owner has administrative control over the workspace and can invite other accounts.

Members access the workspace through an assigned role. The role determines what the member can do inside that workspace.

See Create and use roles for how roles work and which permissions can be assigned.

Invite a member

Only the workspace owner can send invitations.

To invite someone:

  1. Open Workspaces.
  2. Make sure the workspace is the current workspace.
  3. Use the Invite member form on the current workspace card.
  4. Enter the person's email address.
  5. Choose the role they should receive.
  6. Select Send invite.

The recipient receives an invitation email. After accepting it, the workspace appears on their Workspaces page with the assigned role.

Invitations are account-specific owner actions. They are not permissions that can be delegated to API tokens or custom workspace roles.

Tokens and workspace scope

API tokens are created inside the current workspace and use a role from that workspace. Switch to the right workspace before creating a token.

See Create an API token for token creation and storage.

Practical setup

Use separate workspaces when you need clear operational boundaries. Common patterns are:

  • one workspace per environment, such as production and staging;
  • one workspace per product or service group;
  • one workspace per customer or tenant;
  • one workspace per team when teams should not share dashboards or alerts.

Keep owner access limited, and invite members with the narrowest role that fits their work.