---
sourceDocument: Australia Build workflows
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/build-workflows

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Configure content filtering definitions for Playbook

# Configure content filtering definitions for Playbook {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Specify which content a user can access by creating content definitions.

## Before you begin

Content filtering requires some familiarity with user roles and Workflow Studio tables and records.

Role required: admin, playbook.admin

## About this task

Filter Workflow Studio playbook content based on user role. Filtering content requires you to set up:

1. Content definitions describe the content that you want to filter. Content definitions specify types of Workflow Studio resources, such as activity definitions.
2. Content filtering rules to state the role a user must have to access the resource in a particular definition.
{#configure-content-filtering-definitions-playbooks__ol_s14_d5g_2bc}  
There is one content definition for Playbook by default, the Playbooks - All Activity Definitions content definition. The Playbooks - All Activity Definitions content definition has two content filtering rules by default:

* (Default) Playbook - Users with delegated_developer role can access all activity definitions
* (Default) Playbook - Users with playbook.activity_def_read role can access all activity definitions
{#configure-content-filtering-definitions-playbooks__ul_dsg_b3h_2bc}This means that users with the roles delegated_developer or playbook.activity_def_read role can access all activity definitions. Get started with content filtering by using default definitions and rules, or create your own.

## Procedure

1. To modify or create a content definition, navigate to Process AutomationFlow AdministrationContent Definitions.  
   Note:  
   If you don't have access to Flow Administration, the Content Definitions module is directly under Process Automation instead.
2. Select the definition that you want to modify or click New to create one.
3. On the form, fill in the fields.  
   {#configure-content-filtering-definitions-playbooks__steps_nf4_twg_2bc__entry__2}

   | Field | Description |
   |-|-|
   | Name | Name for the content definition. |
   | Application | Application scope to which the content definition applies. This field is automatically set to the currently selected application scope. If no application scope is selected, the field is set to Global. If you set a specific application scope, then the content definition only applies to that application scope. If you select the Global application scope, then the content definition applies to all applications. |
   | Table | Table containing the resource type that you're defining. For example, the Activity Definitions \[sys_pd_activity_definition\] table includes all the activity definitions available on your instance. |
   | Conditions | Conditions used to filter the records in the table. For example, creating a condition where \[Name\] \[contains\] \[Guided Decisions\] returns only the activities that include the term Guided Decisions in the name. |
   | Resource Tags | Tags used to filter the resources in the table. |
   [Table 1. Workflow Resources form]

4. Click Submit.
{#configure-content-filtering-definitions-playbooks__steps_nf4_twg_2bc}

*[\>]: and then