> 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.14/configure-cortex-xsoar/remote-repository-management/install-content-on-a-production-tenant.md).

# Install content on a production tenant

After you push content from the development push tenant, on the right-hand side of any page in the production tenant you have the option to install the content. In case of conflicts, you have a choice whether to keep local content or delete and replace.

1. On the right-hand side of any page, click **Install New Content**.
2. In the dialog box, click **Install Content**.

   You can also check for new content that has been pushed.
3. If conflicts appear, click **Resolve conflicts**.
4. In the **Action** column, select one of the following:
   * **Skip** Keeps the local content in your production environment.
   * **Replace**: Deletes the local content and installs the content from the content repository.
5. Click **OK** to install the content.


---

# 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-xsoar-8-on-prem/8.14/configure-cortex-xsoar/remote-repository-management/install-content-on-a-production-tenant.md?ask=<question>&goal=<endgoal>
```

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