Playbooks roles
Grant users one or more Playbooks roles to enable them to create triggers, playbooks, and activity definitions.
Roles
To learn more about managing per-user subscriptions, see Managing per-user subscriptions in Subscription Management and contact your account representative.
System administrators can grant users access to Playbooks by assigning delegated development permissions or directly assigning Roles. Additionally, playbook authors can create additional filters for runtime user access as they build a playbook in Workflow Studio. The following user roles are available for Playbooks:
| Role | Description |
|---|---|
| playbook.admin | Enables users to:- Create, update, and delete trigger definitions. - Launch Workflow Studio to create, activate, edit, and delete playbooks. - Create, edit, and delete activity definitions. - View the Experience activity types \(sys\_pd\_activity\) and Experience activity properties \(sys\_pd\_activity\_type\_prop\) tables that are shared by Playbooks and Playbook Experience. - Add translations for a playbook. |
| pd\_author | Enables users to:- Launch Workflow Studio to create, activate, edit, and delete playbooks. - View all activity definitions. - View the Experience activity types \(sys\_pd\_activity\) and Experience activity properties \(sys\_pd\_activity\_type\_prop\) tables that are shared by Playbooks and Playbook Experience. |
| pd\_content\_author | Enables users to:- Create, edit, and delete activity definitions. - Create, edit, and delete trigger definitions. - View the Experience activity types \(sys\_pd\_activity\) and Experience activity properties \(sys\_pd\_activity\_type\_prop\) tables that are shared by Playbooks and Playbook Experience. |
| pd\_trigger\_author | Enables users to create, update, and delete trigger definitions. |
| pd\_operator | Enables users to view process executions, activity executions, and execution logs only. |
| pd\_shared.user | Enables users to view the Experience activity types \(sys\_pd\_activity\) and Experience activity properties \(sys\_pd\_activity\_type\_prop\) tables that are shared by Playbooks and Playbook Experience. |
| pd\_shared.admin | Enables users to edit the Experience activity types \(sys\_pd\_activity\) and Experience activity properties \(sys\_pd\_activity\_type\_prop\) tables that are shared by Playbooks and Playbook Experience. |
| pd\_cancel | Enables users to cancel running playbooks without the playbook.admin role or write access to the parent record. For example if you want to grant an agent manager the ability to cancel playbooks, but not an agent. |
| pd\_restarter | Enables users to restart active playbooks. |
| playbook.write | Enables users who have content filtering restrictions to:- Launch Workflow Studio to create, activate, edit, and delete playbooks. - View the Experience activity types \(sys\_pd\_activity\) and Experience activity properties \(sys\_pd\_activity\_type\_prop\) tables that are shared by Playbooks and Playbook Experience. To learn more about content access filtering, see Content filtering for Playbook |
| playbook.designer\_access | Enables users who have content filtering restrictions to launch Workflow Studio to view playbooks. To learn more about content access filtering, see Content filtering for Playbook. |
| playbook.activity\_def\_read | Enables users to view all activity definitions as long as there aren't Required Roles. |
Note: Granting users Playbooks roles does not automatically allow them to access the Workflow Studio design environment. Granting users access to Workflow Studio may be helpful when creating activity definitions. For more information on Workflow Studio roles, see user access to Flow Designer.