---
sourceDocument: Australia Build workflows
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/build-workflows

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Grant delegated access to playbooks

# Grant delegated access to playbooks {#ariaid-title1}

Release version: Australia  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Assign a user as a delegated developer so they can build playbooks within one application.

## Before you begin

Role required: admin

Each user assignment covers one application. Configure the application scope before you assign delegated access.

## About this task

Grant delegated development access when a user should build playbooks inside a single application rather than across the instance. For more information, see [Delegated development access](https://www.servicenow.com/docs/eiYaayBSVGn3ArPBIIRBOQ "Delegated development scopes playbook access to edit Playbook content within a single application, including Playbooks and Activity Definitions. Users can still use activity definitions from other scopes within their playbooks.").

## Procedure

1. Navigate to the application record.  
2. Under Related Links, select Manage Developers.  
3. Search for the user.
4. In the Developers list, locate the user row and enable the Process Automation Designer permission set.  
   To grant all application permissions instead, enable delegated admin access.
5. Save the record.
{#grant-delegated-access-to-playbooks__steps_hqw_b5z_fkc}

## Result

The user receives the delegated_developer role and an application-specific role. To build playbooks, the user must switch from the Global application scope to the scope of this application.