> 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/configure-cortex-xsiam/remote-repository-management/set-up-a-remote-repository.md). # Set up a remote repository When you set up a remote repository, you can use the Cortex XSIAM built-in remote repository, add any private remote repository that is Git-based, or use an on-prem repository. ### Considerations * When you activate a tenant and enable the content repository in Cortex Gateway, Cortex XSIAM by default uses the 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. * When activating a new development tenant in Cortex Gateway for remote repository (adding it to a cluster), all tenants already in the cluster need to be activated and enabled for push/pull. * After the remote repository is enabled in the production tenant as a pull tenant, by default, the first activated development tenant is set to push content to the remote repository. When you add additional development tenants, they are automatically set to pull content from the remote repository. * If the content repository option is disabled for the production or development tenant (under **Settings** → **Configurations** → **General** → **Remote Repository Settings**, toggle the Content repository slider to off), the tenant becomes standalone and does not push or pull content. If you disable the remote repository feature, content on the tenant is not deleted. If you enable the remote repository feature again and the remote repository contains content, you need to choose which content to keep, either the content on the tenant or the content on the remote repository. We recommend backing up any content that you want to keep before enabling again. * When enabling a remote repository in a tenant: * If the relevant repository branch is empty, it inherits the content of the tenant. * If the relevant branch is not empty, you can select which content to keep, either the existing content on your tenant or the existing content on the specified repository. If you want to keep the content on the tenant, you need to first disable the remote repository in the other tenants in the cluster (making them standalone). If even one tenant has remote repository enabled, you can only keep the existing content on the specified repository. * 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 XSIAM platform (for example to implement some scanners) you must use a 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 the different branches you want to use in each tenant. * Activation may take some time. You should receive notification by 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. ### Before you begin * If you are changing your remote repository settings, back up existing content to your local computer by navigating to **Settings** → **Configurations** → **General** → **Server Settings** → **Custom Content** and click **Export all custom content**. * You must have Instance Administrator or Account Admin permission to set up a remote repository. *** --- # 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-xsiam/configure-cortex-xsiam/remote-repository-management/set-up-a-remote-repository.md?ask=&goal= ``` `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.