Task roles in playbooks and projects
Updated
A task role is a job on a project, such as Implementation Lead, IT Contact or Data Owner. It lets a playbook say who a task belongs to without naming a person. Each project then fills in who holds that job.
When to use it
Use task roles when the same kind of person owns the same tasks on every project, but the actual person changes from project to project. Tag the tasks once in the playbook, then pick the people when each project starts.
How it works
Where roles live
Roles are defined once for your whole organization under Settings > Task roles, in the Operations group. To add one, select New role. To learn how to create and edit roles step by step, see Setting up task roles.
Super Admins and Creators can add, edit and archive task roles. Integrators can open the page but only view it. Contributors and Collaborators can't open it at all.
A role has three settings:
Role Name: for example, Implementation Lead.
Role description: optional, but it shows beside the role when you choose people for roles while creating a project.
Is this role for customer users?: makes it a customer role rather than an internal one.
The internal or customer choice is set when you create the role and can't be changed afterwards. Internal roles go only to internal users, and customer roles go only to customer users. Nothing crosses over. That's the usual reason a name is missing from a role's list of people.
Roles in playbooks and modules
You tag roles on individual tasks using the task's Roles field. An internal task offers internal roles, and a customer-facing task offers customer roles. Module tasks have the same Roles field.
If the role you need doesn't exist yet, Super Admins and Creators can select Create task role at the bottom of the list. This opens the Create playbook role dialog. Enter the details there, then select Create role.
Starting a project from a playbook
When you create a project from a playbook that uses roles, you get a step called Choose a coworker for each role. Internal and customer roles are listed separately, each with its description. Assign user to all gives one person every role in a group.
The people you pick become holders of those roles on the new project and are added as project members.
Projects created by workflows fill roles from the workflow's user mapping instead. Setting up task roles explains how that works.
A task is assigned automatically only when its roles resolve to exactly one person. If more than one person holds the role, all of them are set in the task's assignee restrictions, so only they can complete it.
Roles on a live project
You can keep changing roles after a project starts:
The Members tab: a Roles column shows each member's roles. A role filter narrows the list to one role, so you can check who covers a job. Select members to use the bulk Assign role and Remove role actions.
A member's card: has a Roles field you can edit. It's locked while the project is archived, for a member removed from the project, for a member whose account is deactivated, or if you can't manage members.
The add-member dialogs: both include an optional Roles field.
Project tasks: have a Roles field, like playbook tasks.
When a task's role change affects who's assigned, the Add role to task or Remove role from task dialog explains the effect. Its main button reads Add role and users or Remove role and users. To change only the tag, select Add role only or Remove role only.
If you remove a role from the last task that uses it, the dialog offers to remove that role from the people holding it. It tells you how many open tasks they stay assigned to, because removing a role doesn't unassign them.
Apply to ongoing tasks?
The bulk Assign role action on the Members tab grants the role without changing any tasks. Every other way of granting or removing a member's role opens the Apply to ongoing tasks? dialog. Both choices save the role change:
Apply to tasks: granting adds the member to the project's open tasks tagged with that role. A task with no assignee and no restrictions is assigned to them outright. Otherwise they're added to its assignee restrictions. Removing does the reverse, but skips tasks they still reach through another role they hold.
Don't apply to tasks: the role changes, and tasks stay as they are.
You can close the dialog to back out only in two places. When you edit a member's roles in the Members tab table, closing it discards the change. In the add-member dialogs, closing it cancels the add. From a member's card or the bulk Remove role action, the dialog can't be closed, so choose one of the two buttons.
Only open, unarchived tasks are affected. When applying a role assigns tasks to someone outright, they get one assignment email listing those tasks. Each task change is recorded in the task's activity history.
Archiving a role
Archiving a role changes every task that carries it, in playbooks, modules and live projects:
If you choose a replacement, every task tagged with the old role is tagged with the new one.
If you don't, the role is removed from every task that had it.
Either way, the role goes inactive and stops being offered.
People who hold the role keep it. That's why a project's Roles column can show Name (archived).
OnRamp offers a replacement only when the role is used in playbooks or modules, and you don't have to pick one. Archived roles are listed under the Archived filter on the Task roles page.
Limits
You can't switch a role between internal and customer after it's created.
Unarchiving a role makes it selectable again, but doesn't restore tags that archiving removed or replaced. Unarchiving fails if an active role already has the same name.
Applying a role to tasks never changes completed or archived tasks.
Name roles after the job, not the person. Data Owner works on every project; Dana's tasks doesn't. Fill in the description, since it's the context people see when choosing who fills the role.