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


---

# Restrict access by playbook type

# Restrict access by playbook type {#ariaid-title1}

Release version: Australia  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Use content access filtering to give a group of users access only to playbooks of a specific type.

## Before you begin

Role required: admin, playbook.admin

The playbook type you want to filter by must exist.

## About this task

Restrict access by playbook type when a group of users should work with one category of playbook and no others. A business unit that owns its own playbook types can be given access to those types alone.

This uses the same content access filtering mechanism that restricts activity definitions. For more information, see [Content filtering for Playbook](https://www.servicenow.com/docs/sWYxlsggbvQwCiqV~qd3TA "Specify which content a user can access based on the user's role.").

## Procedure

1. Create a role for the users who need this access.  
   Use a descriptive name that identifies the group and the access, for example, a role named for the business unit and the read operation.
2. Create a content definition for the playbooks.
   1. Navigate to Process AutomationFlow AdministrationContent Definitions.  
      The Workflow Resources table opens.
   2. Select New.
   3. Set Table to the playbook table.
   4. In Conditions, add a condition on playbook type.
   5. Select Submit.
   {#restrict-playbook-access-by-type__substeps_pwr_txz_fkc}
3. Create a content filtering rule that connects the role to the content definition.
   1. Navigate to Process AutomationFlow AdministrationContent Filtering Rules.  
      The Workflow Resource Filter Rules table opens.
   2. Select New.
   3. Set User Role to the role you created.
   4. Set Resource Definition to the content definition you created.
   5. Select Submit.
   {#restrict-playbook-access-by-type__substeps_qwr_txz_fkc}
4. Assign the role to the users who need this access.
{#restrict-playbook-access-by-type__steps_owr_txz_fkc}

## Result

Users with the role see only playbooks of the type named in the content definition. Playbooks of other types aren't visible to them.

## What to do next

Pair this with the playbook.write role rather than pd_author. The pd_author role grants access to all playbooks and overrides the restriction. For more information, see [Role-based access](https://www.servicenow.com/docs/ggpv51UzX5llf_jVNiiIww "Assign roles to control who can view, create, and edit playbooks.").

*[\>]: and then