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

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Configure runtime permissions for a playbook

# Configure runtime permissions for a playbook {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Add permission sets to a playbook to restrict who can view and act on it at runtime.

## Before you begin

Role required: playbook.admin, pd_author

## About this task

Permissions configured at playbook level apply to the whole playbook unless a stage overrides them. For an explanation of how permissions combine, see [Runtime permissions](https://www.servicenow.com/docs/hPAN3t~u2lumiWZxWtd6zA "Runtime permissions restrict who can read, restart, cancel, and add optional activities to a running playbook.").  
Note:  
The default parent record requirements always apply. Permissions you add here narrow access further and can't widen it.

## Procedure

1. Navigate to AllWorkflow StudioPlaybooks.
2. Open the playbook that you want to restrict.
3. From the More actions menu, select Properties.  
4. Select Runtime permissions.
5. Review the Parent record permissions.  
6. Add permissions and select its source.
   1. Select Add permission set to restrict an operation.  
   2. Grant the permission set by User, User group, Roles, or a User criteria record.  
   3. Select View to grant general access to the playbook.
   4. **Optional:** Select Manage to open and configure additional runtime options.
   5. **Optional:** Select Trigger on-demand to grant access to view the record generator before the playbook is triggered.  
   6. Select the Add permission set icon ![Green check mark icon]() when you're done configuring the permission.  
   7. **Optional:** Select Add permission set to add more permissions to the same operation.  
      Permissions added to one operation combine with OR, so any one of them satisfies it.
   {#configure-runtime-permissions-playbook__substeps_sxl_vhr_rkc}
7. Select Save and close.
{#configure-runtime-permissions-playbook__steps_rv2_ng5_gkc}

## Result

Users must satisfy the default parent record requirement and at least one permission you added for each operation you restricted.

## Example: Restricting a playbook to expert agents {#configure-runtime-permissions-playbook__example_hvj_szr_rkc}

For example, a case resolution process has two playbooks: a detailed L1 playbook for newer agents, and a shorter L3 playbook for expert agents. Add a permission set to the L3 playbook that names the expert role or a user
criteria record, so only those agents can access it at runtime.

## What to do next

Reactivate the playbook. Permission changes affect new executions after reactivation, not existing executions.
**Related tasks**   

* [Apply runtime permissions for a stage](https://www.servicenow.com/docs/3Pr4w8KX7lJeoq875PMmbg "Add permission sets to one stage to give the stage different runtime access from the rest of the playbook.")

*[\>]: and then