---
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


---

# Apply runtime permissions for a stage

# Apply runtime permissions for a stage {#ariaid-title1}

Release version: Australia  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Add permission sets to one stage to give the stage different runtime access from the rest of the playbook.

## Before you begin

Role required: playbook.admin, pd_author

## About this task

By default, anyone who has read or write access to a parent record has access to a stage. Restrict permissions at the stage level when one stage needs access rules that the playbook as a whole doesn't. A stage that handles
sensitive data can require a role that the rest of the playbook doesn't require.

Permission sets you add at stage level must also have read access at playbook level. A user who meets the stage criteria but has no playbook-level access can't read the stage. Where a stage has no override, the playbook-level
permissions apply.

## Procedure

1. Navigate to AllWorkflow StudioPlaybooks.
2. Open the playbook that you want to work on.
3. On the diagram view, select the stage you want to restrict.
4. Select Additional runtime permissions.  
5. Review the inherited permissions.
6. Add permissions to an operation and select the source.
   1. Select Add permission set to restrict an operation.  
      You can restrict access to the stage at the Read the stage, Add optional activities, Restart the stage, and Restart the activity operational level.
   2. Grant the permission set by User, User group, Roles, or a User criteria record.  
   3. Select the Add permission set confirmation ![Green check mark icon]().  
   4. **Optional:** Select Add permission set for the same operation to add more permissions.  
      Permissions added to one operation combine with OR, so any one of them satisfies it.
   {#override-runtime-permissions-stage__substeps_sxl_vhr_rkc}
7. Select Add permission set next to another operation to add permissions to a different operation.
8. Select Save and close to save your work on the playbook runtime permissions.

## Result

The permissions you set on the stage further narrow the playbook-level permissions for that stage. Activities within the stage inherit the stage permissions.

## What to do next

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

* [Configure runtime permissions for a playbook](https://www.servicenow.com/docs/s_G26toNBKhh_XOuwG1xIw "Add permission sets to a playbook to restrict who can view and act on it at runtime.")

*[\>]: and then