---
schema_version: "1"
id: de4ba74c4f552daa64508f3dcd0082fd35cd86f70f9ae0e5bd643ded2f135bb1
title: Package Data Cloud Metadata Components
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/platform-pkg-exchange/managed_packaging/guides/second-generation/dev2gp-package-data-cloud.md
canonical_url: https://developer.salesforce.com/docs/platform/pkg2-dev/guide/dev2gp-package-data-cloud.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: dc5528ed2295dc5ce88f238eecced9f4ac72f67049102dc4a1379c5d1e494d74
products:
  - Second-Generation Managed Packaging Developer Guide
  - merged-docs
---

# Package Data Cloud Metadata Components

Utilize the power of Data Cloud in your apps by including Data Cloud metadata in your managed packages. Working with Data Cloud metadata has some unique requirements. Review these details to understand how to work with Data Cloud metadata in your packages.

## Enable Data Cloud for Scratch Orgs

To create scratch orgs or package Data Cloud components, you must have Dev Hub enabled in your Partner Business Org. Then, you can request that Data Cloud for Scratch Orgs be enabled by logging a case with [Salesforce Partner Support](https://partners.salesforce.com). Data Cloud for Scratch Orgs is only available to scratch orgs associated with the Dev Hub in your Partner Business Org.

## Create Dedicated Data Cloud Packages

When creating a managed package with Data Cloud metadata, you must isolate the Data Cloud metadata from the other Salesforce metadata by creating separate packages that contain only Data Cloud metadata. Then create package dependencies between your dedicated Data Cloud package and any related packages.

## Add Data Cloud Metadata to a Data Kit

When packaging Data Cloud metadata, you must add the metadata to a data kit, and then add the data kit to the managed package. Data kits streamline the package creation and installation process. For more details, see [Packages and Data Kits](https://developer.salesforce.com/docs/platform/data-cloud-dev/guide/packages-data-kits.html) in the _Data Cloud Developer Guide_.

## Data Cloud One Companion Connected Orgs

Packages can’t be installed on orgs that are connected to Data Cloud as Data Cloud One companion orgs. When Data Cloud customers install a managed package containing Data Cloud metadata, they must install the package in their Data Cloud home org. For customers using Data Cloud One, any package installed into data spaces shared with a companion org are automatically installed into the companion org. Companion orgs automatically receive package updates when the package in the home org is upgraded.

These package-related actions can’t be initiated in companion connected orgs, and must instead be initiated in the Data Cloud One home org.

- Installing a managed package
- Uninstalling a managed package
- Deleting package metadata
- Receiving a package push upgrade

**See Also**

- [_Data Cloud Developer Guide_: Get Started with Data Cloud Development](https://developer.salesforce.com/docs/platform/data-cloud-dev/guide/get-started.html)
- [_Data Cloud Developer Guide_: Workflow for Data Cloud Second-Generation Managed Packages](https://developer.salesforce.com/docs/platform/data-cloud-dev/guide/data-cloud-2gp-workflow.html)
- [_Data Cloud Developer Guide_: Metadata Components for Data Cloud Cheat Sheet](https://developer.salesforce.com/docs/platform/data-cloud-dev/guide/component-cheatsheet.html)
- [_Salesforce Help_: Connect Salesforce CRM Orgs to Data Cloud](https://help.salesforce.com/s/articleView?id=data.c360_a_connect_salesforce_orgs.htm&type=5)