Push content to a remote repository and control access for pushing content.
Once you develop your content, for it to be available as part of a content update for the production tenant, you must push the changes from the development tenant.
Caution
Do not manually export content from the development tenant to import to the production tenant. Use only the procedures outlined in the documentation to ensure that your content is properly updated in the production tenant.
We do not recommend pushing content from a development tenant to a production tenant if they have different versions. This helps avoid compatibility conflicts, versioning errors, and unintended behavior in the production environment.
On each page, you can decide whether to include or exclude items to push to production, on a temporary or permanent basis. You can only exclude individual content items, not content packs.
The following types of content can be synchronized between development and production tenants:
Note
In the production tenant, it is not possible to edit these content items.
In the development tenant, go to → .
Under the Local Changes section, go to the relevant page according to the items you want to push:
Items
Content that is not related specifically to a content pack. For example, customized scripts or playbooks. When creating custom content, the content is automatically added here. If you have already pushed a content pack and later edited one of its content items, the edited items appear on the Content Pack Items page, not the Content Packs page.
Content Packs
All of the content is specific to the content packs you installed from Marketplace.
Content Pack Items
If you do not want to install the whole content pack, you can install specific items in the content pack.
Note
If your development tenant runs a different version of Cortex XSOAR than your production tenant, Cortex XSOAR displays warnings and visual indicators for potential version mismatches when syncing content between development and production.
When pushing a content pack to the production tenant, we recommend pushing all content of the content pack to work properly.
If you have reordered your pre-processing rules you must push all of the pre-processing changes to the production tenant.
Select the items you want to push to production, and click Push.
If the items have dependencies, review the contents and click Push
Sometimes you may not want to push all content, content pack dependencies, etc. For example, when a user makes a change in a playbook that includes a script dependency to which another user is adding a feature, and the change does not require the new feature (version) of the script, you can push the playbook without the new script.
In the dialog box, add an optional message and click Push.
On the production tenant, Install content on the production tenant.