---
schema_version: "1"
id: 647407da7853f564ce6a448e72ccf60c665cc430dfeae6102ba92cccf8ce2824
title: Packages
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/marketing-cloud/guides/mc-app-development/packages-overview.md
canonical_url: https://developer.salesforce.com/docs/marketing/marketing-cloud/guide/packages-overview.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 01bdf7d1bc149a6f335fef225f98e33d15378fffc64501c4f4ac6919766fa9c5
products:
  - Marketing Cloud Engagement APIs and Programmatic Languages
  - Marketing Cloud
---
# Packages

**note:** Ensure that you have the Installed Package | Administer permission. This permission is automatically applied to the Administrator and Marketing Cloud Engagement Administrator system-defined roles. Add the permission for a role or user under Administration in Setup.

A package is a container of functionality for something as small as an individual component or as large as a set of related apps. After creating a package, you can administer and distribute it to other users and business units within your account.

You can install packages into your account, and then configure and manage them. To view the packages installed in business units where you have permission to install and manage packages, go to **Setup | Apps | Installed Packages**.

Each package has one or more components that determine what the package can do. Use packages to create API integrations, install custom apps, or add custom Journey Builder components.

## Example 1 - API Integration Component

You create an integration with a third-party application, which needs access to the REST API or SOAP API. To get a client ID and secret, create an installed package with an API Integration component. You can have one API integration per package.

## Example 2 - App Component

You create an external app and iFrame it into Marketing Cloud Engagement. Create an installed package with an App component. You can have one app per package. If your app needs access to the API, create an API Integration component as well.

## Example 3 - Journey Builder Activity Component

You need a custom activity for one of your journeys that kicks off a REST API call in a third-party application. Create an installed package with a Journey Builder Activity component. You can have multiple Journey Builder Activities per package.

## Example 4 - Journey Builder Entry Source Component

You need a custom entry source for one of your journeys that comes via a REST API call from a third-party application. Create an installed package with a Journey Builder Entry Source component. You can have multiple Journey Builder Entry Sources per package.

## Example 5 - Custom Content Block Component

Instead of using Content Builder's CKEditor WYSIWYG for HTML editing, you'd like to use a different WYSIWYG, like QuillJS. Create an installed package with a Custom Content Block component.

## Related Items

- [AppExchange](https://appexchange.salesforce.com/results?filter=15)
- [Roles](https://help.salesforce.com/articleView?id=mktg.mc_overview_roles.htm)