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. The following user roles are available for Playbooks:
| Role | Description |
|---|---|
| pd_admin | Enables users to create, update, and delete trigger definitions. Also enables users to launch the Playbooks environment to create, activate, edit, and delete playbooks, activity definitions, and trigger definitions. |
| pd_author | Enables users to launch the Playbooks environment to create, activate, edit, and delete playbooks. |
| pd_content_author | Enables users to create, edit, and delete activity definitions and trigger definitions. |
| 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 pd_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. |
Note:
Granting users Playbooks roles does not automatically allow them
to access the Flow Designer design environment. Granting users access to
Flow Designer may be helpful when creating activity definitions. For more
information on Flow Designer roles, see user access to Flow
Designer.