> 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-xsiam/insights-and-tips-cortex-xsiam/automation-and-integrations/playbook-versioning-and-promotion.md).

# Playbook versioning and promotion

Manage Cortex XSIAM playbook versions, test safely, and promote automation content between tenants.

### Version history

* **Playbooks:** Save a version with a description from the menu next to **Save Playbook**. Open **Version history for all Playbooks** to see the commit message, change type, date, and author, and **Restore** a previous version. See [Manage playbook content](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/automations/playbooks/build-your-playbook/manage-playbook-content.md).

{% hint style="info" %}
Autonomous playbooks are versioned and updated by Palo Alto Networks. You cannot edit, duplicate, or promote them.
{% endhint %}

* **Scripts:** The scripts page shows version history for recently modified or deleted scripts.
* **Audit log:** Creation, modification, and deletion of playbooks and rules are recorded in the management audit log.

### Test before production

Use the **Playground**, a non-production investigation that isn't connected to a live case, to run commands, scripts, and integrations safely. Playground access is controlled by Playground permissions. See [Playground permissions](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/reference-and-developer-docs/role-based-access-control/investigation-and-response-permissions/automation-permissions/playground-permissions.md).

{% hint style="info" %}
Test AI-generated content and new custom agents and actions in a development tenant.
{% endhint %}

### Move content between tenants

| Need                              | Method                                                                                                                                                                                                                                                                                                                                 |
| --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| One-time copy                     | **Settings** → **Configurations** → **General** → **Server Settings** → **Custom Content**: export all custom content as a bundle, then upload it in the destination tenant. See [Configure server settings](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/onboard-cortex-xsiam/post-deployment/configure-server-settings.md). |
| Ongoing development-to-production | Connect a built-in or private Git **remote repository**. Push from the development tenant, and pull in production. See [Push and pull content](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/remote-repository-management/push-and-pull-content.md).                                                    |
| Reuse within a tenant             | Use sub-playbooks and custom content packs.                                                                                                                                                                                                                                                                                            |

{% hint style="info" %}
Dashboards, lists, parsing rules, data model rules, and correlation rules aren't supported by remote repository push and pull. Export them separately. Avoid pushing between tenants that run different versions.
{% 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 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-xsiam/insights-and-tips-cortex-xsiam/automation-and-integrations/playbook-versioning-and-promotion.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.
