---
title: "Publishing Content Packs | ThreatConnect"
slug: "publishing-content-packs"
description: "This article describes how System Administrators on ThreatConnect Cloud can install a Content Pack and then publish it to the TC Exchange catalog. It also provides best practices to follow before publishing a Content Pack."
updated: 2023-06-20T12:33:32Z
published: 2023-06-20T12:33:32Z
canonical: "knowledge.threatconnect.com/publishing-content-packs"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.threatconnect.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Publishing Content Packs

If you are a System Administrator on [ThreatConnect® Cloud](https://app.threatconnect.com/), you can publish a Content Pack to the TC Exchange™ catalog after installing it by toggling the Content Pack’s **Allow App Distribution** setting on. Doing so allows you to easily distribute the Content Pack to the broader ThreatConnect customer base.

## Best Practices for Publishing Content Packs

This section provides some best practices to follow *before* publishing a Content Pack:

- Add summaries, descriptions, and labels to [Playbooks](https://knowledge.threatconnect.com/docs/playbooks), as this helps customers identify which Playbooks belong to a given Content Pack. Similarly, use proper names and labels for [Playbook Components](https://knowledge.threatconnect.com/docs/playbook-components) and Component variables used in the Playbooks.
- Confirm that all Playbooks are using the latest versions of Apps, and replace all [deprecated Apps](https://threatconnect.readme.io/docs/deprecated-apps).
- Ensure that each Playbook’s layout is well organized, as this allows customers to understand and follow a Playbook’s logic when they open it in the [Playbook Designer](https://knowledge.threatconnect.com/docs/the-playbook-designer).
- Remove keychain and environment variables linked to a specific machine, server, or environment from each Playbook.
- Install the Content Pack on another ThreatConnect instance, import its Playbooks into your Organization from the System-level [Playbook Templates](https://knowledge.threatconnect.com/docs/playbook-templates) created during the Content Pack installation process, and test the Playbooks to verify that they run successfully.
- When [creating a Content Pack](/docs/creating-content-packs), include the description parameter and an accompanying description of the Content Pack in the body of the API request. Doing so will provide customers with a description of the Content Pack when they view it on the **Catalog** tab of the **TC Exchange Settings** screen.

## Publishing Content Packs on ThreatConnect Cloud

1. Log into ThreatConnect Cloud ([app.threatconnect.com](https://app.threatconnect.com/)) with a System Administrator account.
2. On the top navigation bar, hover over **Settings**![Settings icon](https://cdn.document360.io/dfc206c8-1c9f-4725-b74d-a66f83432320/Images/Documentation/Settings%20icon.png)and select **TC Exchange Settings**. The **Installed** tab of the **TC Exchange Settings** screen will be displayed.
3. Click the **+ Add New** button at the top right of the **TC Exchange Settings** screen to [install a Content Pack](/docs/installing-content-packs) using a **.tcxp** file.
4. After the Content Pack is installed, select **Content Packs** from the dropdown to the left of the search bar on the **Installed** tab of the **TC Exchange Settings** screen to display only installed Content Packs.
5. Click on the vertical ellipsis in the **Options** column for the Content Pack and toggle the **Allow App Distribution** setting on (Figure 1).  
![Figure 1_Publishing Content Packs_7.1.2](https://cdn.document360.io/dfc206c8-1c9f-4725-b74d-a66f83432320/Images/Documentation/Figure%201_Publishing%20Content%20Packs_7.1.2.png)

After completing these steps, the Content Pack will be displayed on the **Catalog** tab of the **TC Exchange Settings** screen for all other ThreatConnect instances.

---

*ThreatConnect® is a registered trademark, and TC Exchange™ is a trademark, of ThreatConnect, Inc.*

20152-04 v.01.A