> 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.14/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/playbooks/version-control.md).

# Version Control

Save and manage Cortex XSOAR 6.14 playbook versions during development.

You can save versions of a playbook as you are developing it. When you save a version of a playbook, add a meaningful comment so that you will be able to recognize the changes you made in that version at a later time. The version is saved with the name of the playbook, your commit message, an indication of what the change was (modify, insert, etc.), the date the playbook was saved, and the name of the author who last saved it. If necessary, you can access the playbook’s version history and revert your playbook to a previous version.

1. From the Save Playbook dropdown list, click **Save version for current Playbook**.

   ![playbook-version-control.png](https://3548014557-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOHlpKeFtqCLUYKuYyccd%2Fuploads%2Fgit-blob-d331046022ee23922ef07dc0b84ee1b849f06fce%2F57ee2a4df30d33647b29a963b68ea0bd4fcb3c9ae0780e5a1c2517978c959e25.png?alt=media)
2. Enter a description of the change that was made to the current version.
3. Click **Update Playbook**.
4. To access a version of a playbook:
   1. Click **Version history for all Playbooks**.

      ![playbook-version-history.png](https://3548014557-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOHlpKeFtqCLUYKuYyccd%2Fuploads%2Fgit-blob-ae183e93cd2aaecce6043af9cc3f2077cb30f114%2F21ef59233d1bcdd6a38c396471b75e94ed20429752cc242a499576849a9b13c8.png?alt=media)
   2. Search for the required playbook. The description that was entered when the version was saved should help you locate the version you now require.

      ![playbook-version-history-table.png](https://3548014557-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOHlpKeFtqCLUYKuYyccd%2Fuploads%2Fgit-blob-90d4840e617d5c692bee8c7b8e1f69a2bb7870aa%2F78c9d47f0067211af1f098b6f247388a4fcd5ff9e7eab8b009f2ee441a6f8ca6.png?alt=media)
   3. Click **Restore** to open the required version of the playbook.


---

# 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/xsoar-6-administrator-guide/6.14/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/playbooks/version-control.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.