> 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-6-multi-tenant-guides/6.13/configure-multi-tenant/remote-repositories-for-multi-tenant-deployments/configure-a-remote-repository-on-the-main-account.md). # Configure a Remote Repository on the Main Account To work with the remote repositories, you must have one machine configured as your [development machine](/cortex-xsoar-6-multi-tenant-guides/6.13/configure-multi-tenant/remote-repositories-for-multi-tenant-deployments/configure-a-remote-repository-on-a-development-machine.md), and the main account configured as your production environment. **Prerequisites** Before configuring the remote repository, review the following list of prerequisites: * Ensure that the Selective Propagation feature is enabled. It should be enabled by default. * Verify that the content that you want already exists in the remote repository. You cannot edit content in the main account. All of the content is fully synchronized with the remote repository.

Note

Any content that exists in the main account, but not on the remote repository, will be deleted

1. **Define the repository**. 1. Navigate to Settings → Advanced → **Content Repository**. 2. Click the On/Off slider to enable the remote repositories. The main account is automatically defined as the Production environment. This cannot be changed. 3. Enter the URL and connection credentials to the repository. Only SSH connections are supported.

Note

If you are using a passphrase, only RSA private keys are supported.

If your SSH connection uses a port other than port 22 (the default SSH port), you must include the ssh string and port number in the url. In the following example, we use port 20017: **`ssh://git@content.demisto.com:20017/~/my-project.git`** 4. Select the active branch from which you pull content. 5. Click **Save**. In the Discard server changes screen, you are presented with content that exists in your production environment, but does not exist on the remote repository. This includes integrations, and their instances and classifiers. ![remote-discard-server.png](/files/ewqHkqNusyL4D1xNOUA1) 6. Type **`Discard`** in the relevant field and click **Continue**. All of the content that appears in this screen is discarded and permanently deleted. Content from the remote repository is installed. This can take several minutes depending on the amount of content in the remote repository and your hardware configuration. In addition, your custom content is automatically backed up to the Cortex XSOAR server any time you change one of the remote repository settings. The backup is located under `/var/lib/demisto/backups/content-backup-*.tar.gz.` 2. **Pull Content from the Remote Repository** After you push content from the Development machine to the remote repository, it is available as an update for the main account. 1. Check for updates. 2. Click **Install 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-6-multi-tenant-guides/6.13/configure-multi-tenant/remote-repositories-for-multi-tenant-deployments/configure-a-remote-repository-on-the-main-account.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.