> 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.13/configure-cortex-xsoar/playbooks/develop-your-playbook/task-7.-manage-playbook-content.md).

# Task 7. Manage playbook content

Manage playbook content in Cortex XSOAR 8.13 On-prem.

Manage playbook content by either using a remote repository, or by saving versions of your playbook in Cortex XSOAR to maintain version history. For more details, see [Manage playbook content](/cortex-xsoar-8-on-prem/8.13/configure-cortex-xsoar/playbooks/manage-playbook-content.md).

Cortex XSOAR also manages playbook editing conflicts by only allowing one user at a time to edit a playbook and locking it for other users to edit. It automatically clears the playbook edit lock when the user currently editing the playbook saves the playbook, closes the editor, logs out, or when their session expires. In addition, you can grant a permission to designated users so they can manually unlock playbooks from the **Playbooks** page or editor.


---

# 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 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/cortex-xsoar-8-on-prem/8.13/configure-cortex-xsoar/playbooks/develop-your-playbook/task-7.-manage-playbook-content.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 `automate deployments from our CI pipeline` 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.