---
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 content filtering rules

# Configure content filtering rules {#ariaid-title1}

Release version: Brazil  
Updated October 5, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Create a rule that grants a role access to the content in a content definition.

## Before you begin

Role required: admin, playbook.admin

A content definition must exist. See [Configure content filtering definitions](https://www.servicenow.com/docs/ufAYb9uMaHsams_2lJKxLg "Create a content definition that describes a set of content a filtering rule grants access to.").

## About this task

A content filtering rule associates one or more roles with a single content definition. Users with the named role can reach the content covered by the definition, unless the content has required roles set. For more
information, see [Content access filtering](https://www.servicenow.com/docs/1TZyxLL_QV2wIX_moHK70A "Restrict access to subsets of playbook content by pairing a content definition with a filtering rule.").

## Procedure

1. Navigate to Process AutomationFlow AdministrationContent Filtering Rules.  
   The Workflow Resource Filter Rules table opens.

   If you don't have access to Flow Administration, Content Filtering Rules appears directly under Process Automation.
2. Select an existing rule or select New.
3. Fill in the form.  
   {#configure-content-filtering-rules-playbook__table-filtering-rule-fields__entry__2}

   | Field | Description |
   |-|-|
   | Name | Name of the rule. |
   | User Role | Role a user must have to reach the content. |
   | Delegated Development Permission | Optional. The resource path for which the user is a delegated developer. |
   | Active | Whether the rule is in force. |
   | Application | Application the rule belongs to. Defaults to the current scope. |
   | Resource Definition | Content definition the rule grants access to. |
   [Table 1. Content filtering rule fields]

   {#configure-content-filtering-rules-playbook__table-filtering-rule-fields}
4. Select Submit.
{#configure-content-filtering-rules-playbook__steps_irz_dxz_fkc}

## Result

Users with the named role can reach the content covered by the definition. Assign playbook.write rather than pd_author to those users, because pd_author grants access to all content and overrides the restriction because of a
default, unmodifiable content filtering rule.

*[\>]: and then