Project manager is a project role, not a workspace role. It is set per project on the project's Members tab, next to the plain Member role. A Member of the workspace who is Project manager on a project runs that project's membership and settings without needing the Admin role. Owners and Admins act as manager on every project automatically.
Before you start
You need the Project manager role on the project, given by an Owner, Admin, or an existing workspace-user Project manager on the project's Members tab. Everything a Workspace member can do still applies; this page lists only what the role adds.
What the role adds
- Edit the project's name and description under the project's Settings tab. See Create a project.
- Add and remove workspace users on the project, and choose their role (Member or Project manager). See Manage project members.
- Elevate client users: adding a client user to the project elevates them there. "Elevation is usable once they have a password or passkey login." Users of any client on the project can be elevated.
- Add collaborating clients to the project, so their users can be elevated and tickets can be billed to them. See Collaborating clients.
- Set a consultant category override per member in the Category column of the Members tab. New time entries by that person on this project snapshot the override instead of their workspace default. See Consultant categories and rate cards.
- See the project's client timesheets under Documents: the documents produced for this project, without a client-wide grant. "A project manager without it sees only their own project artifacts." See Client timesheets.
Ticket permissions do not change. A Project manager edits, moves, assigns, and archives tickets on the project exactly like a Member does.
What still needs an Owner or Admin
| Task | Why |
|---|---|
| Set or change the Billing client | Decides who is billed; Owner or Admin only |
| Set the Billing mode (Per period / When the ticket closes) | Same |
| Archive the project | Owner or Admin. Projects are never deleted. |
| Create a new project | Owner or Admin |
| Create clients or client users | Owner or Admin. A manager can only elevate client users who already exist on a client that is on the project. |
| Rate cards, policies, time banks for the client | Owner or Admin |
The message for these is "Only owners and admins can do this."
When the manager is a client user
An elevated client user can be given the Project manager role too. Their powers are narrower than a workspace-user manager's:
- They can elevate only users of their own client ("You may only elevate users of your own client."), and only when that client is on the project.
- They cannot add collaborating clients.
- They cannot add or remove workspace users.
- They cannot edit the project's name or description.
- They see documents only if they are also a billing contact.
All of this works only in a full-login session; in a magic-link session the client user is regular again and the manager role is inert.
Example
Kari is a Member of the acme workspace and Project manager on the project Acme website. She adds her colleague Ola as a Member, adds Acme's Per (a client user) so he is elevated on the project, sets Ola's category to Senior consultant for this project, and downloads last month's timesheet for the project under Documents. When Acme asks to have the project billed to a different Acme entity, she asks an Admin: changing the billing client is outside her role.