code0Vörr AIContactGuides
Book a Demo
Guides/Shankh/Getting Started

Create workspaces, members and teams

WorkspacesBeginner6 min

A workspace groups the people and services in the same incident-response flow. A team is the group inside a workspace that escalation actually addresses. Both are created in Workspaces.

AdminCreating workspaces and teams and managing members requires Admin access.

Create a workspace

  1. Open Workspaces.
  2. Select New Workspace.
  3. In the Create Workspace panel, enter the name — use the team or ownership boundary it represents, such as Platform or Payments.
  4. Choose the primary engineer.
  5. Select Create.
Workspaces — create, rename, switch or delete

Name is the only field the service itself requires. The primary engineer is enforced by the interface and saved by a second call right after creation, so a workspace created outside the UI can exist without one.

Add or invite members

  1. Expand the workspace in Workspaces.
  2. Select Add member to add an existing organisation user, or use the invite-by-email option for someone new.
  3. Assign Admin or Member access.
  4. Send the invitation if inviting by email.
  5. Confirm the person appears in the workspace list.
A workspace expanded — the member list, roles and the Add existing member tab

An invited user only joins after accepting. Until then they cannot receive incidents from this workspace.

Choose the right role

Admin
Reads Shankh data, creates and changes configuration, manages workspaces, teams and members, configures alerting, escalation and cloud integration, and can acknowledge and resolve incidents.
Member
Has read access to configuration and incident data, cannot change administrative configuration, and can acknowledge and resolve incidents.

Members participate fully in incident response, so keep Admin for the people who actually need to change configuration.

Create teams for the workspace

Teams are created on the Escalation page, not on Workspaces.

  • Give a team one clear responsibility, so escalation is unambiguous.
  • Keep at least two people in any team an escalation step depends on.
  • Remove people who have left the rotation — a stale or empty team silently absorbs an escalation step.
  1. Open Escalation and go to the Manage Teams tab.
  2. Select Create Team.
  3. Enter the Team name — the only field you fill in; the workspace is shown read-only.
  4. Select Create.
  5. Add the members once the team exists — members are not part of the create step.
A team is empty the moment it is created. Add its members before you attach it to an escalation level.

Verify the setup

  1. Confirm every responder is in the workspace that owns their services.
  2. Confirm at least one Admin remains in each workspace.
  3. Confirm every responder belongs to at least one team, and no team is empty.
  4. Confirm invited users accepted before you rely on them for coverage.