Get Started as Team Lead

Persona: Team Lead

Summary

The Team Lead gets started in Hub through one of two paths: being invited to an existing workspace as Workspace Admin, or being onboarded as a Workspace Manager who can create their own workspaces.

---

Path A: Invited to an Existing Workspace as Workspace Admin

Context: CoE Admin has created a workspace and added the Team Lead as Workspace Admin (see Onboard Organisation Members). The Team Lead receives a notification and takes over the workspace.

1. Receive workspace invitation notification — Team Lead is notified they have been added to a workspace as Workspace Admin.
2. Open workspace — Logs into Hub. The user is navigated to the Workspace they were added to.
3. Review workspace — Reviews the workspace and the initial setup. Checks:
   • Workspace name and description.
   • Current members and their roles.
   • Assigned clusters (visible clusters scoped by CoE Admin).
4. Adjust membership if needed — Adds or removes members, adjusts roles to reflect the actual team composition.
5. Create projects — Creates one or more projects within the workspace. Optionally organises files and folders within each project.
6. Assign projects to clusters — Configures each project’s deployment target from the available clusters. Only clusters visible to this workspace appear in the selection.
7. Kick off the development — Notifies the team that the workspace is ready. Developers can start working.

---

Path B: Onboarded as Workspace Manager — Create and Set Up Workspace

Context: CoE Admin has added the Team Lead to the organisation with the Workspace Manager role (see Onboard Organisation Members). The Team Lead can now create and manage their own workspaces.

1. Receive notification — Team Lead is notified that they were added to the organisation with the Workspace Manager role.
2. Log into Hub — Opens Hub. Sees the organisation view. No workspaces are assigned yet.
3. Create a workspace — Creates a new workspace. Sets workspace name and description.
4. Add team members — Invites or adds team members to the workspace and assigns workspace roles (Editor, Commenter, Viewer).
5. Create projects — Creates one or more projects within the workspace.
6. Request cluster assignment — The Team Lead does not have permission to assign clusters to workspaces. Submits a request to CoE Admin to assign clusters to the workspace.
7. Clusters become available — Once the CoE Admin assigns clusters, the Team Lead configures deployment targets for projects.
8. Kick off the development — Notifies the team that the workspace is ready. Developers can start working.

---

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