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


---

# Restrict access to an activity definition

# Restrict access to an activity definition {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Limit which users can add a specific activity definition to a playbook.

## Before you begin

Role required: playbook.admin

## About this task

Set Required Roles when an activity is sensitive and only certain roles should use it. Required roles override content access filtering, so a user without the required role can't use the activity definition even when a content filtering rule grants access to it.  
Note:  
Both the playbook.admin and pd_content_author roles can edit activity definitions, but only the playbook.admin role can edit the Required Roles field.

## Procedure

1. Navigate to Process AutomationPlaybook AdministrationActivity Definition.
2. Select the activity definition you want to restrict access to.
3. In the Required Roles field, add the roles that a user must have to use this activity definition.
4. Select Update.

## Result

Users without one of the required roles can't select the activity definition when they build a playbook. Playbooks that already contain the activity definition open read-only for those users.

*[\>]: and then