User access to Playbooks in Workflow Studio

Administrators can grant users access to Playbook by assigning delegated development permissions or directly assigning a user role. Administrators can also specify which features and content a user can access based on user roles.

Access by user role

Administrators can grant access to Playbook in Workflow Studio by directly assigning users the pd_author user role, which includes the role to view activity definitions.

Table 1. Roles for Playbook in Workflow Studio

Role	Description	Contains Roles
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.	pd_author pd_content_author pd_trigger_author pd_operator pd_cancel
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_shared.user playbook.write playbook.activity_def_read
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 pd_shared.user playbook.activity_def_read
pd_trigger_author	Enables users to create, update, and delete trigger definitions.	none
pd_operator	Enables users to view process executions, activity executions, and execution logs only.	none
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.	none
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_shared.user
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.	none
pd_restarter	Enables users to restart active playbooks.	none
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.	pd_shared.user
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.	pd_shared.user
playbook.activity_def_read	Enables users to view all activity definitions as long as there aren't Required Roles.	none

A visual representation of where roles are contained:

• playbook.admin
  • pd_content_author
    • playbook.activity_def_read
    • pd_shared.user
    • pd_trigger_author
  • pd_operator
  • pd_cancel
  • pd_restarter
  • pd_author
    • playbook.write
      • playbook.designer_access
        • pd_shared.user
        • sn_workflow_studio.workflow_studio_read
          Note:

          This role allows users to launch Workflow Studio, and is not managed by playbook administrators.
        • sn_diagram_builder.db_read
          Note:

          This role allows users to view playbooks in the diagram view in Workflow Studio, and is not managed by playbook administrators.
    • playbook.activity_def_read
  • pd_shared.admin
    • pd_shared.user
• delegated_developer

Delegated development access

Administrators can grant users access to Workflow Studio playbooks by creating an application and assigning users as developers with the playbook delegated development permission. Delegated development allows administrators to control whether playbook authors can access features normally restricted to admin users. For more information, see Developer permissions.

Role-based content filtering

Specify the user roles necessary to access Workflow Studio playbook content. For example, activity definitions and process definitions. Manage content filtering by creating content definitions and content filtering rules. For more information, see Content filtering for Playbook.

Role-based activity definition access

Manage activity definition access by specifying the Required Roles to access an activity definition. Users who can view the playbook but who do not have the required role to access activities with this activity definition will have a read-only view of the playbook.

To learn more about activity definitions, see Create an activity definition and Activity definitions.

Note:

Both playbook.admin and pd_content_author roles can edit activity definitions, but only the playbook.admin role can edit the Required Roles field.

• Content filtering for Playbook
  Specify which content a user can access based on the user's role.
• Configure content filtering definitions for Playbook
  Specify which content a user can access by creating content definitions.
• Configure content filtering rules for Playbook
  Use content filtering rules to specify the role a user must have to access content.