> 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-saas/onboard-cortex-xsoar/deployment-steps/step-3.-set-up-a-remote-repository.md).

# Step 3. Set up a remote repository

When you set up a remote repository, you can use the Cortex XSOAR built-in remote repository, or use a private content repository (Git-based, including GitHub, GitLab, and Bitbucket) to test and develop content. In Cortex Gateway, you activate a development tenant from the production tenant. All content from your production tenant is copied to the development tenant. When the content is ready, you can push the content to the production tenant.

{% hint style="info" %}

### Note

* In a cluster of tenants that includes one production tenant and one or more development tenants, only one development tenant pushes. 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 activated development tenant 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.
* In a multi-tenant environment, development tenants can only be activated from the Main Tenant. They are not available for child tenants. Child tenants receive content from the Main Tenant and have no connection to a development tenant.
  {% endhint %}

#### 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.
* You must have a development tenant license.
* Activate the development tenant. For more information, see step 8 in [Activate Cortex XSOAR](/cortex-xsoar-8-saas/onboard-cortex-xsoar/deployment-steps/step-1-activate-cortex-xsoar.md).

#### Set up the remote repository in Cortex XSOAR

You can set up one of the following repositories:

* Built-in remote repository

  When you activate a tenant and enable the content repository in Cortex Gateway, Cortex XSOAR by default uses the built-in repository. The built-in remote repository requires fewer configurations than using a private remote repository and cannot be accessed directly. If you want to use a private remote repository, you need to configure it when you enable the remote repository in the tenant.

  For a simple one-branch deployment, we recommend using the built-in repository. If you want to use multiple branches, or if you need access to the content repository outside the Cortex XSOAR platform (for example, to implement some scanners) you must use a private repository.

  For more information, see [Set up a built-in remote repository](/cortex-xsoar-8-saas/configure-cortex-xsoar/remote-repository-management/set-up-a-remote-repository/set-up-a-built-in-remote-repository.md).
* Private repository

  If you want to use a private remote repository with one or more branches, you need to enable the remote repository in each tenant and then set up all branches in the remote repository configuration page in Cortex XSOAR.

  For more information, see [Set up a private remote repository](/cortex-xsoar-8-saas/configure-cortex-xsoar/remote-repository-management/set-up-a-remote-repository/set-up-a-private-remote-repository.md)

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

Activation may take some time. You should receive an email that the production or development tenant has completed the activation process.

Once the activation completes, you can only change content repository settings within the tenant.

To learn more about remote repositories, requirements, and configuration, see [Content management in Cortex XSOAR](/cortex-xsoar-8-saas/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-saas/onboard-cortex-xsoar/deployment-steps/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.