> 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-agentix/configure-cortex-agentix/automations/playbooks/manage-playbooks.md). # Manage playbooks The **Playbooks** page helps you access playbooks for your use cases. It shows summary details at the top and your Org repository table below. ### Playbook status Playbook statuses help you track automation progress and identify delays. The status shows how many playbooks: * Are in your Org repository * Are enabled * Are active * Use an automation rule * Are used as sub-playbooks * Ran during the last week ### The Org repository table The Org repository table lists playbooks your organization adopted or built. It shows: * Playbook name, description, status, source, and tags * Associated enabled and disabled automation rules * Sub-playbook use, last update details, and content pack Right-click a playbook to open it in the editor, duplicate it, disable it, download it, or remove it. Playbooks in **Org Playbooks** can run through automation rules, jobs, or manual issue runs. Adopted playbooks belong to content packs. When you adopt one, its content pack is downloaded and appears in Marketplace. Removing a playbook does not uninstall its content pack. The playbook then becomes unavailable for automation rules and manual runs. ### Playbook Catalog The **Playbook Catalog** contains all the playbooks available in Marketplace, organized by cards. You can search for specific playbooks in the **Search by** filter according to the following criteria: * **Everywhere (default)**: Searches for the specified keyword across all fields, including the playbook name, description, and tags. * **Name**: Limits the search to the title of the playbook. * **Description**: Searches within the playbook's detailed description for matching terms. * **Tag**: Filters playbooks by specific metadata tags assigned to them. * **Content pack**: Filters the catalog to show only playbooks that belong to a specific content pack. Clicking a playbook card provides a preview of the playbook. If it is relevant for your use case, click **Adopt this playbook** to bring it into your Org repository and make it available to run. {% hint style="info" %} * The library initially shows only unadopted playbooks. Select **Show Adopted** to include adopted playbooks. * The library displays the latest version. Adopt an older version through Marketplace. * Adopting a playbook does not run it. Content packs can include recommended automation rules. See [Create an automation rule](/cortex-agentix/configure-cortex-agentix/automations/create-an-automation-rule.md). {% endhint %} --- # 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-agentix/configure-cortex-agentix/automations/playbooks/manage-playbooks.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.