> 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.5/onboard-cortex-xsoar/onboard-and-configure-cortex-xsoar/step-3.-set-up-a-remote-repository.md).

# Step 3. Set up a remote repository

When you set up a remote repository, you can add any private content repository that is Git-based, including GitHub, GitLab, and Bitbucket. Also, On-prem repositories are supported.

Although you can set up multiple development tenants, in a cluster of tenants that includes one production tenant and one or more development tenants, only one development tenant can push content. The production tenant and any other development tenants pull from the one development tenant that is configured to push content. After the remote repository is enabled in the production tenant, by default, the first development tenant that has been installed is set to push content to the remote repository. When you create additional development tenants, they are set to pull content from the remote repository.

If the content repository option is disabled for the production or development tenant, the tenant becomes standalone and does not push or pull content.

#### Before you begin

* If you are changing your remote repository settings, back up existing content to your local computer by navigating to Settings & Info → Settings → System → Server Settings → **Custom Content** and click **Export all custom content**.
* You must have Instance Administrator or Account Admin permission.

#### Install a development tenant

1. If you haven't done so already, download and install the Cortex XSOAR development tenant.
   1. From the Cortex Gateway, in the **Available for Activation** section, use the serial number to locate the development tenant to download.
   2. Click **Re-Download On Prem**.
   3. Select **Dev** and click **Next**.
   4. Select the relevant image file.

      <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>Note</h3><p>Although you must select the same image file you downloaded for production, you can use a different platform for the development tenant. For example, if you have downloaded an OVA file and installed the VM on AWS in the production tenant, you can install the VM on OCI in the development tenant.</p></div>
   5. Agree to the terms and conditions and select **Download**.
   6. Install Cortex XSOAR according to the image file downloaded. For more information about installation, see [Installation overview](/cortex-xsoar-8-on-prem/8.5/onboard-cortex-xsoar/cortex-xsoar-installation.md).

      <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>Important</h3><p>In the textual UI menu, when you reach the <strong>Cluster Installation</strong> stage, select <strong>Enterprise</strong> in the <strong>Installation Mode</strong> field. You must select this mode when installing production or development tenants.</p></div>
   7. Add the non-production license (included in the installer).
2. After you install the development tenant, you can set up the private remote repository. For more information, see [Set up a private remote repository](/cortex-xsoar-8-on-prem/8.5/configure-cortex-xsoar/remote-repository-management/set-up-a-private-remote-repository.md).

To learn more about remote repositories, requirements, and configuration, see [Content management in Cortex XSOAR](/cortex-xsoar-8-on-prem/8.5/configure-cortex-xsoar/remote-repository-management/content-management-in-cortex-xsoar.md).


---

# 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.5/onboard-cortex-xsoar/onboard-and-configure-cortex-xsoar/step-3.-set-up-a-remote-repository.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.