Project-bound role

When creating a role you can tick Bound to a project (or other entity). Members are then assigned per project, so each project can have its own project manager. Important: approval policies cannot resolve a project-bound role, so nobody can approve a step that relies on one – use a team-wide role for approvals.

Team-wide role (the default): members fill the role for the whole team – for example members of Accounting can decide on every bill.

Project-bound role: membership applies to one specific project.

1. In the New role dialog, tick Bound to a project (or other entity) and choose Project as the Scope type.
2. In the Add member dialog, next to the user enter the number of the project the membership applies to in the Scope id field.

Approval policies currently work with team-wide roles only. If a step refers to a project-bound role, nobody can decide on that step and nobody is notified about it; the Approval Policies page flags this as an incomplete setup.