Prerequisites for the Playbooks
concept australia Updated Sep 10, 2026 1 min read getting-started-with-processes.md
You need the following roles and plugins to build the Playbooks.
Role required: admin.
- Enable the Process Automation Designer (PAD) [com.glide.pad.license] plugin.
- Enable the following plugins for a playbook experience:
- com.playbook_experience
- now_playbook_exp
- com.glide.playbook_experience.config
- Enable Security Operations spoke to access flows [com.snc.secops.spoke].
- Enterprise Security Case Management PAD Commons.
Make sure that you have read the platform documentation on Exploring Playbook and Process Automation Designer before you start with this guide.
Parent Topic:Using SIR Workspace
Related topics
Using ServiceNow Otto for Security Incident Response (SIR) generative AI skills
Working with Security Incident Records
Rebuilding existing playbooks in Workflow Studio
Sample Playbooks for SIR Workspace
58 lines · 2.2 KB
---
title: Prerequisites for the Playbooks
description: You need the following roles and plugins to build the Playbooks.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/security-management/security-incident-response/getting-started-with-processes.html
release: australia
product: Security Incident Response
classification: security-incident-response
topic_type: concept
last_updated: "2026-09-10"
reading_time_minutes: 1
breadcrumb: [Use, Security Incident Response Workspace, Security Incident Response, Enterprise security case management applications, Security Operations]
---
# Prerequisites for the Playbooks
You need the following roles and plugins to build the Playbooks.
Role required: admin.
- Enable the Process Automation Designer \(PAD\) \[com.glide.pad.license\] plugin.
- Enable the following plugins for a playbook experience:
- com.playbook\_experience
- now\_playbook\_exp
- com.glide.playbook\_experience.config
- Enable Security Operations spoke to access flows \[com.snc.secops.spoke\].
- Enterprise Security Case Management PAD Commons.
Make sure that you have read the platform documentation on [Exploring Playbook](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/process-automation-designer.md) and [Process Automation Designer](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/process-automation-designer.md) before you start with this guide.
**Parent Topic:**[Using SIR Workspace](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/security-incident-response/using-sir-workspace.md)
**Related topics**
[Using ServiceNow Otto for Security Incident Response \(SIR\) generative AI skills]()
[Using agentic AI workflows]()
[Working with Security Incident Records]()
[Security Incident Playbook]()
[Rebuilding existing playbooks in Workflow Studio]()
[Activity Definitions]()
[Sample Playbooks for SIR Workspace]()
[Working with MSI Records]()
[Working with Form UI actions]()
[Security Incident Closure workflow]()
[Handle security incidents using Advanced Work Assignment]()
| title | Prerequisites for the Playbooks |
| description | You need the following roles and plugins to build the Playbooks. |
| locale | en-US |
| canonical_url | https://www.servicenow.com/docs/r/australia/security-management/security-incident-response/getting-started-with-processes.html |
| release | australia |
| product | Security Incident Response |
| classification | security-incident-response |
| topic_type | concept |
| last_updated | 2026-09-10 |
| reading_time_minutes | 1 |
| breadcrumb | UseSecurity Incident Response WorkspaceSecurity Incident ResponseEnterprise security case management applicationsSecurity Operations |