---
sourceDocument: Xanadu Build workflows
sourceDocumentLink: https://www.servicenow.com/docs/r/xanadu/build-workflows

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Playbooks roles

# Playbooks roles {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Grant users one or more Playbooks roles to enable them to create triggers, playbooks, and activity definitions.

## Roles {#process-automation-designer-roles__section_zs5_mfw_blb}

To learn more about managing per-user subscriptions, see [Managing per-user subscriptions in Subscription Management](https://www.servicenow.com/docs/access?context=managing-user-subscriptions-v2&version=xanadu&pubname=xanadu-platform-administration&ft:locale=en-US) and contact your account representative.

System administrators can grant users access to Playbooks by assigning [delegated development permissions](https://www.servicenow.com/docs/access?context=c_DelegatedDevelopment&version=xanadu&pubname=xanadu-application-development&ft:locale=en-US) or directly assigning [Roles](https://www.servicenow.com/docs/access?context=exploring-user-administration&version=xanadu&pubname=xanadu-platform-administration&ft:locale=en-US). The following user roles are available for Playbooks:  
{#process-automation-designer-roles__table_h1y_drx_blb__entry__2}

| 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. {#process-automation-designer-roles__ul_sxd_4lw_cbc} |
| 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. {#process-automation-designer-roles__ul_vpt_qmw_cbc} |
| 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. {#process-automation-designer-roles__ul_bgn_fqw_cbc} |
| 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 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. {#process-automation-designer-roles__ul_zv4_1nw_cbc} |
| playbook.activity_def_read | Enables users to view all activity definitions. |
[ ]

{#process-automation-designer-roles__table_h1y_drx_blb}  
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](https://www.servicenow.com/docs/VUD4NOLjFa0QlvbERnriWA "Administrators can grant users access to Workflow Studio flows 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. Application developers can access Workflow Studio functionality through APIs for flows, subflows, and actions.").