---
schema_version: "1"
id: 8ea81f3899a37153e3e3f464ec59a0af023114b566f3c62b5fa0de1d6640195e
title: Package CRM Analytics Assets in Managed Packages
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/analytics/264-0-0/bi_packaging_package.md
canonical_url: https://help.salesforce.com/s/articleView?id=analytics.bi_packaging_package.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: e101e131d000851360915fe74243126488d1097d9218e6390175b7dbae7de380
description: You can create managed packages of CRM Analytics assets, including CRM Analytics apps, dashboards, lenses, datasets, recipes, dataflows, and user XMD. Use packages to distribute those assets to other users within or outside your company.
products:
  - CRM Analytics
  - Cross Cloud
release: "264"
---
# Package CRM Analytics Assets in Managed Packages

You can create managed packages of CRM Analytics assets, including CRM Analytics apps, dashboards, lenses, datasets, recipes, dataflows, and user XMD. Use packages to distribute those assets to other users within or outside your company.

A package is a container for something as small as an individual component or as large as a set of related apps. Packages can be distributed to other Salesforce users and organizations, including outside your company. While packages come in two forms—unmanaged and managed—CRM Analytics supports only managed packages, which must be created from a Developer Edition organization.

Why only managed packages? There are some key advantages, especially around licensing and managing licenses. Using AppExchange and the License Management Application (LMA), partners, ISVs, and developers can sell and manage user-based licenses for the app. Managed packages are also upgradeable, meaning you don’t have to start over; you can incrementally upgrade.

To package CRM Analytics assets:

1. From Setup in your Developer Edition org, select **Packages** and click **New** to [create a managed package](https://developer.salesforce.com/docs/atlas.en-us.pkg1_dev.meta/pkg1_dev/uploading_packages.htm).
2. Click **Add** in the Components tab, then from the Component Type dropdown list, select and add your CRM Analytics assets to the package. Each component type is prefixed Analytics. Add dependent dataflows manually. That is, if you add a dataset to a package, the associated dataflows aren’t automatically picked up.
    
    ![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-analytics-bi-264-0-0-production-enus/ec791473-f5b4-4f64-a656-9104f455d966/images/icon_important.png)
    
    Important Analytics components include Analytics applications, dashboards, dataflows, datasets, lenses, recipes, and user XMD.
    
    ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-analytics-bi-264-0-0-production-enus/ec791473-f5b4-4f64-a656-9104f455d966/images/icon_note.png)
    
    Note All custom fields used in a deployed dataflow must exist on the target org. The Analytics Cloud Integration User user must have access to the custom fields.
3. To ensure all dependent assets and appropriate [permission sets and profile settings](https://developer.salesforce.com/docs/atlas.en-us.pkg1_dev.meta/pkg1_dev/distribution_perm_sets_profile_settings.htm) are added, click **View Dependencies**.
4. After your apps are packaged, [prepare them for distribution](https://developer.salesforce.com/docs/atlas.en-us.pkg1_dev.meta/pkg1_dev/uploading_packages.htm).

#### See Also

- [_Salesforce DX Developer Guide_: Managing Licenses for Managed Packages](https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/lma_intro.htm)