> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.12/configure-cortex-xsoar/playbooks/develop-your-playbook/task-2.-configure-playbook-settings.md). # Task 2. Configure playbook settings Configure playbook settings as relevant, including: * Name and description * Tagging * Access * Whether to associate the playbook with an incident type. This needs to be set under the **Settings & Info** → **Settings** → **Object Setup** → **Incidents** → **Types** tab. * Whether to run the playbook in Quiet Mode ### How to configure playbook settings 1. Go to **Playbooks** and click the playbook that you want to edit. 2. If it is a content pack playbook, detach or duplicate the playbook by clicking the ellipsis icon. If you detach the playbook and want to keep any changes, ensure that you duplicate the playbook before reattaching. 3. Click the settings wheel icon. 4. Edit the following settings as relevant. 1. In the **BASIC** section, change the name and description.

Note

You cannot change the name of a detached playbook.

2. Add any tags as required by either typing a new tag or selecting from the list. Tags help you search for a particular playbook, such as Malware. 3. Add roles for edit access to the playbook. 4. If you want to disable a playbook, deselect the **Enabled** checkbox. If disabled, you cannot associate it with an incident or an incident type. 5. In the **ADVANCED** section, determine whether the playbook runs in quiet mode. When **Quiet Mode** is selected, playbook tasks do not display inputs and outputs and do not extract indicators. Playbook tasks are not indexed so you cannot search on the results of specific tasks. All of the information is still available in the context data, and errors and warnings are written to the War Room.

Tip

Quiet mode is recommended for scenarios that involve a lot of information that might adversely affect performance, for example, processing indicators from threat intel feeds.

In the War Room, you can run the **!getInvPlaybookMetadata** command to analyze the size of playbook tasks in a specific incident Work Plan to determine whether to implement quiet mode for playbooks or tasks. 5. Click **Save all tabs**. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.12/configure-cortex-xsoar/playbooks/develop-your-playbook/task-2.-configure-playbook-settings.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.