Leadership walkthrough · Chapter 3 of 8
People, and the project manager
Asha creates the people who will do the work: first Ravi, the project manager, then Meena, Karthik and Divya, reporting to Ravi. Then Asha gives Ravi the Manager role on the account so Ravi can start projects there.
A person's manager approves their leave and decides when an allocation would overbook them. Create Ravi first, and Ravi can be chosen as the team's manager. Ravi then holds the Line manager template automatically, because having direct reports confers it.
Create Ravi, the project manager
- Open People and choose New resource. As an account owner, Asha's People page lists only the people Asha has created.
- Fill in the record.
- First name, Last name and Email, the address the login goes to.
- Designation: Account Product Manager. This is the designation an account owner can give a project manager. It carries no template on its own, so it gives nothing until Ravi has a role on the account.
- Manager: leave empty for Ravi.
- Joined: optional. Weeks before it carry no capacity, so nobody can reserve them.
- Leave Send login now on. Ravi receives the invitation. Turn it off to add someone now and send the login later from People.
- Choose Create resource.
The form also has Status, Department and Branch. Asha can't pick a shift, so the default shift is applied.
Create the team, reporting to Ravi
- Choose New resource again for Meena. Designation: a delivery role such as Senior Software Engineer. Manager: Ravi.
- Repeat for Karthik and Divya. Same manager.
- Many people at once? Import beside New resource takes a spreadsheet: upload, match columns, run a dry-run check that shows what would happen to every row, then import.
Giving a designation also gives its template, so PMO Assist only lets Asha give designations whose template Asha's own access covers. Asha can give Account Product Manager and ordinary delivery designations. Asha can't give Product Manager, Delivery Manager, Resource Manager or Workspace Manager, because those carry rights across the whole organisation. PMO Assist refuses and names what is missing.
Give Ravi the Manager role on the account
- Open Accounts, then Northwind Retail, then the Members tab.
- Choose Add member.
- Person: Ravi. Role: Manager. The dialog explains each role as it is chosen.
- Confirm with Add member in the dialog. Ravi can now see every project under Northwind Retail, and create projects there and nowhere else.
Give Daniel, from sales, a read-only view
Executives and sales follow an account without working in it. They are stakeholders: they have a login but no resource profile.
- An administrator invites Daniel. People›Invite stakeholder. Inviting a stakeholder needs the rights to manage logins and grant permissions, which an account owner doesn't hold.
- Asha adds Daniel to the account as Viewer. Accounts›Northwind Retail›Members›Add member, Role: Viewer.
Daniel now sees the account's health, milestones, releases and published reports. Daniel never sees work items or sprints, and never sees anything unpublished.
Where things stand
| Person | Holds | So they can |
|---|---|---|
| Asha | Account owner template · Owner of Northwind Retail | Run the account and lead every project under it; manage the people Asha created. |
| Ravi | Account Product Manager · Manager of Northwind Retail · Line manager of the team | Create projects under Northwind Retail; approve the team's leave and overbooking. |
| Meena, Karthik, Divya | Resource profiles, reporting to Ravi | Sign in, see every resource, and work on the projects they join. |
| Daniel | Viewer of Northwind Retail | Read the delivery picture and published reports. |
Now the projects. Chapter 4.