Persona: CoE Admin
Summary
A Team Lead requests a new workspace for a newly formed delivery team. The CoE Admin reviews the request against governance policies and approves or rejects it.
Steps
- Receive workspace request notification — Hub notifies CoE Admin that a Team Lead has submitted a workspace creation request.
- Review request details — Opens the request. Reviews:
- Proposed workspace name and purpose.
- Requested team members.
- Required clusters (dev, staging, production).
- Justification and business domain.
- Validate against policies — Checks whether the request aligns with governance rules:
- Does the name follow the taxonomy?
- Is there a legitimate need for a separate workspace (vs. joining an existing one)?
- Are cluster assignments reasonable?
- Approve or Reject:
- Approve: Workspace is created. During the creation flow, CoE Admin assigns clusters to the workspace. Optionally adjusts initial membership. Team Lead is notified.
- Reject: Provides feedback explaining why. Team Lead is notified.
- Refine cluster assignments (if needed) — After creation, CoE Admin can manage cluster associations from the Organisation → Clusters page (cluster-centric) or the Organisation → Workspaces management page (workspace-centric).
See also: Governed Workspaces with Cluster Associations - E2E User Journeys