> 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/xsoar-6-administrator-guide/6.15/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/playbooks/manage-playbook-settings.md).

# Manage Playbook Settings

Configure Cortex XSOAR 6.15 playbook settings, access, triggers, and Quiet Mode.

You can manage general playbook settings such as the name of the playbook, who can edit and run the playbook, and whether Quiet Mode is turned on. To change the settings, click **Edit** and then click the gear icon.

{% hint style="info" %}
You can update the roles and enable/disable the playbook in **View** mode (without clicking **Edit**).
{% endhint %}

You can set the playbook to **Quiet Mode** to improve system performance. In Quiet Mode, playbook tasks are not indexed, so you cannot search on the results of specific tasks. Entries are not written to the War Room, and inputs and outputs are not presented for Work Plan tasks. All of the information is still available in the context data, and errors and warnings are written to the War Room.

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

{% hint style="info" %}
When creating a new custom playbook, by default, the playbook is set to **Quiet Mode**.
{% endhint %}

You can run [the `!getInvPlaybookMetadata` command](/xsoar-6-administrator-guide/6.14/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/playbooks/manage-playbook-settings/obtain-playbook-metadata.md) to analyze the size of playbook tasks to determine whether to implement quiet mode for playbooks or tasks.

1. From the **Playbooks** page, click the playbook that you want to manage.
2. In a content pack playbook, detach or duplicate the playbook by clicking the ellipsis icon.

   If you want to reattach a playbook and keep any changes, ensure that you duplicate the playbook before reattaching.
3. Click **Edit**.
4. Click the settings wheel icon.
5. Edit the following settings as required.

   1. In the **Basic** section, change the name and description.

      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 dropdown list.

      Tags help you search for a particular playbook, such as Malware.
   3. In the **Roles** field, from the dropdown list, select the roles for which the playbook is available.
   4. If you want to disable a playbook, uncheck the **Enabled** checkbox.

      If disabled, you cannot associate it with an incident or 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-settings.png](https://content.gitbook.com/content/8xEMUKpU65o1wagTHaO3/blobs/gCG7RJcavgON2I6JgLKd/d32cfa117dd26855b01dc7d490607332590870b1f3db368519235123f12b0039.png)
6. 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 following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.15/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/playbooks/manage-playbook-settings.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.