Assign runtime permissions while creating sequences

task australia Updated Sep 10, 2026 1 min read configure-runtime-permission-sequence-playbooks.md

Use permission sets to control access to sequence records such as sequence tasks and steps.

Before you begin

Delegated developer roles must be assigned to designated users. For more information, see Grant delegated developer permissions for managing sequences.

Note: Runtime permissions are available only with at least Playbooks version 28.1 on the Zurich release. For more information, see Playbooks in Workflow Studio release notes.

Role required: sn_crm_sequence.admin, sn_crm_sequence.writer

Note: If you're using Customer Engagement Sequences 1.0.0, you need the playbook.admin or pd_author role to create sequences.

Procedure

Navigate to Workspaces > CRM Workspace.
Select the List icon [Omitted image "list-outline-24.svg"] Alt text:.
Navigate to Sequences > All Sequences.
Select a sequence that you're creating or updating.
On the Workflow Studio page, select Properties from the More actions menu icon [Omitted image "icon-three-dot-menu.png"] Alt text:.
On the Playbook properties window, select Runtime permissions.
Grant fine-grained access to sequence records by selecting a permission set from the Add permission set menu.

The available permission sets are:
- Users
- User groups
- User criteria
Use the data pill picker to establish a connection between a user, user group, or criteria with a column on the parent table.

To allow agents to view only their own assigned sequence tasks for a sequence based on the Lead table, you would select Parent Record as Lead and then its Owner column. For instance, if user Max Blaze is overlooking a lead, only Max Blaze will be able to view the sequence steps and complete activities.
Confirm your selection and set the permission by selecting the Add permission set icon[Omitted image "circle-check-outline-24.svg"] Alt text:.
Grant the level of access by selecting View or Manage or both.
Add additional permission sets as needed.
Select Save and close.

Parent Topic:Create a customer engagement sequence

Customer Engagement Sequences

70 lines · 3.4 KB Wrap lines

---
title: Assign runtime permissions while creating sequences
description: Use permission sets to control access to sequence records such as sequence tasks and steps.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/order-management/configure-runtime-permission-sequence-playbooks.html
release: australia
topic_type: task
last_updated: "2026-09-10"
reading_time_minutes: 1
breadcrumb: [Create sequences, Customer Engagement Sequences, Sales automation apps, Use, Sales Customer Relationship Management]
---

# Assign runtime permissions while creating sequences

Use permission sets to control access to sequence records such as sequence tasks and steps.

## Before you begin

Delegated developer roles must be assigned to designated users. For more information, see [Grant delegated developer permissions for managing sequences](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/order-management/grant-delegated-developer-permissions.md).

**Note:** Runtime permissions are available only with at least Playbooks version 28.1 on the Zurich release. For more information, see [Playbooks in Workflow Studio release notes](https://www.servicenow.com/docs/r/zurich/release-notes/process-automation-designer-rn.html).

Role required: sn\_crm\_sequence.admin, sn\_crm\_sequence.writer

**Note:** If you're using Customer Engagement Sequences 1.0.0, you need the playbook.admin or pd\_author role to create sequences.

## Procedure

1. Navigate to **Workspaces** &gt; **CRM Workspace**.

2. Select the List icon \[Omitted image "list-outline-24.svg"\] Alt text:.

3. Navigate to **Sequences** &gt; **All Sequences**.

4. Select a sequence that you're creating or updating.

5. On the Workflow Studio page, select **Properties** from the More actions menu icon \[Omitted image "icon-three-dot-menu.png"\] Alt text:.

6. On the Playbook properties window, select **Runtime permissions**.

7. Grant fine-grained access to sequence records by selecting a permission set from the **Add permission set** menu.

The available permission sets are:

- Users
- User groups
- User criteria
8. Use the data pill picker to establish a connection between a user, user group, or criteria with a column on the parent table.

To allow agents to view only their own assigned sequence tasks for a sequence based on the Lead table, you would select Parent Record as Lead and then its **Owner** column. For instance, if user Max Blaze is overlooking a lead, only Max Blaze will be able to view the sequence steps and complete activities.

9. Confirm your selection and set the permission by selecting the Add permission set icon\[Omitted image "circle-check-outline-24.svg"\] Alt text:.

10. Grant the level of access by selecting View or Manage or both.

11. Add additional permission sets as needed.

12. Select **Save and close**.

**Parent Topic:**[Create a customer engagement sequence](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/order-management/create-customer-engagement-sequence.md)

**Related topics**

[Configuring Customer Engagement Sequences](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/order-management/configuring-customer-engagement-sequences.md)

[Customer Engagement Sequences](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/order-management/explore-customer-engagement-sequences.md)