Camunda Hub

Set Up New Delivery Team

Personas: CoE Lead, CoE Admin

Summary

The CoE Lead defines workspace strategy and governance policies, then the CoE Admin executes the plan in Hub by creating workspaces, assigning clusters, and onboarding team leads.

Steps

CoE Lead: Establish Workspace Strategy

(Largely happens outside Camunda Hub)

  1. Assess Organisational Landscape — Reviews the current state: how many teams exist, what domains they cover, and what clusters are provisioned. Identifies that the flat structure does not scale.
  2. Define Workspace Taxonomy — Designs a workspace structure that maps to business domains or delivery teams (e.g., “Payments Team”, “Onboarding Team”, “Shared Services”). Documents naming conventions and purpose for each workspace.
  3. Define Governance Policies — Establishes rules for workspace creation:
    • Only Org Admins can create workspaces (no self-service sprawl).
    • Every workspace must have a designated Team Lead as Workspace Admin.
    • Workspace naming must follow the agreed taxonomy.
    • Clusters are assigned per workspace — no global visibility for non-admins.
  4. Define Cluster Assignment Strategy — Maps which clusters (dev, staging, production) should be visible to which workspaces. Decides whether teams share clusters or get dedicated ones.
  5. Brief a CoE Admin — Hands off the workspace plan, governance rules, and cluster assignment map to the CoE Admin for execution in Hub.
  6. Onboard Team Leads — Communicates the new structure to Team Leads.

CoE Admin: Create Workspace and Onboard Team

  1. Log Into Camunda Hub — Opens Hub and navigates to the Organisation-level view.
  2. Create workspace for new delivery team — Navigates to Workspaces. Creates new workspaces based on the approved taxonomy:
    • Sets workspace name and description.
    • Assigns a Team Lead the Workspace Admin role.
    • Optionally adds initial members with workspace roles (Editor, Commenter, Viewer).
    • Assigns clusters — selects which clusters the workspace can access.
    • Confirms workspace creation.
  3. Automatic notifications to workspace members — Workspace members are notified that they were added to the workspace.
  4. Communicate readiness internally — (Optionally) Internally informs the CoE and Team Lead that the workspace is ready.

See also: Governed Workspaces with Cluster Associations - E2E User Journeys

Graph View

Backlinks