Push Content from a Development Tenant - Administrator Guide - 8 - Cortex XSOAR - Cortex - Security Operations

Cortex XSOAR Administrator Guide

Cortex XSOAR
Creation date
Last date published
Administrator Guide

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.

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.

On each page you can decide whether to include or exclude items, which prevents them from being pushed to production, on a temporary or permanent basis. You can only exclude individual content items, not content packs.


You can configure a development push tenant so that only admins can push content to the remote repository. For more details, see Server Configurations.Server Configurations

  1. In the development tenant, go to Settings & InfoSettings.

  2. 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 edit one of its content items, the edited items appear in the Items page, not the Content Packs page.

    • Content Packs

      All of the content that 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.

  3. Select the items you want to push to production, and click Push.

  4. 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.

  5. In the dialog box, add an optional message and click Push.

  6. On the production tenant, Install Content on a Production Tenant.