> 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/remote-repositories-overview.md).
# Remote Repositories Overview
Cortex XSOAR supports the ability to work with separate repositories for a development environment and main account. This enables you to develop and test all of your content in one location, and when it is ready, you push the content to the main account. In your main account, you pull the content as you would all other content updates, and push content to your tenants using [selective propagation](/cortex-xsoar-6-multi-tenant-guides/6.13/configure-multi-tenant/manage-content.md).
In addition, Cortex XSOAR content updates are only delivered to the development environment. This enables you to determine which updates you want to push to the main account.
{% hint style="info" %}
### Note
Working with remote repositories is Git-based. Any service that supports this protocol can be used, for example, GitHub, GitLab, Bitbucket, etc. In addition, on-premise repositories are also supported.
{% endhint %}
**How it Works**
In the main account, the content appears as a content update, just like any other, and you pull the content from the remote repository into your working branch.
To work with remote repositories, you must have two separate Cortex XSOAR environments on two separate machines. The development environment is used to write the following content:
* Automations
* Playbooks
* Integrations
* Classifiers
* Mappers
* Lists
Note
Lists created in the development environment and pushed to production cannot be edited in the production environment. Lists created in the production environment can be edited in the production environment.
Note
When pushing a content pack to the remote repository, you should push all of its content, listed in the Local Changes window, for the content pack to work properly.
Note
If you have more than two pre-processing rules in your Local Changes queue, you must push all of those changes to the remote repository.