Establish a Data Cloud One Companion connection between the Data 360 org and another Salesforce org. You can't create a companion connection to a Salesforce org that's already connected to another Data 360 via a companion connection. You also can't connect a sandbox org to a production org.
Required Editions
| Available in: All Editions supported by Data 360. See Data 360 edition availability. |
| User Permissions Needed | |
|---|---|
| Set up the connection from the home org |
Standard System admin profile AND Data Cloud Architect permission set |
| Authorize the connection from the companion org | Standard System admin profile |
The connection must be initiated from the home org. When prompted during setup, log in to the companion org by using System Admin credentials.
Before you set up a companion connection:
-
Plan your Data 360 architecture strategy.
-
Review Data 360 Architecture Strategy for architectural considerations.
-
Choose a home org where Data 360 is provisioned.
-
Choose a companion org. (A Salesforce org that already has Data 360 provisioned can't be connected as a companion org). If your intended companion org already has Data 360, deprovision Data 360 on that companion org first. See Convert a Data 360 Home Org to a Data Cloud One Companion Org.
-
-
Verify that the companion org you're connecting has a Data Cloud One Companion license. If not, add one by using Your Account.
-
Configure the domain settings in the home org and companion org to support the connection.
-
Confirm that both orgs have API access and allow the Salesforce IP range. See Salesforce IP addresses and domains to allow.
If you don't want users to log in to your org through your instanced URL, go to the My Domain page in Setup and select Don't redirect for your instanced URL in the redirections section.
When you create a Data 360 companion connection, a standard Salesforce CRM org connection is also created. If you already have a Salesforce CRM connection to the org that you're connecting, the standard connection's name is updated to match the companion connection's name.
To initiate the connection, use the following steps.
- From the Setup menu in the home org, select Data Cloud Setup.
-
Select Data Cloud One, and click
New.
If you reached your org's maximum number of companion org connections, use Your Account in the home org to add a Data Cloud One Additional Connection license, and then try again.
- When prompted during the connection process, log in to the companion org with System Admin credentials.
- Review the org summary to confirm that you're connecting to the correct org, and click Next.
-
Select one or more data spaces to share with the companion org, and click
Next. Metadata is synced only in data spaces that you share with
this companion org. If no data spaces are shared, metadata isn't ingested or synced.
Note If you’re not sure which data space to use, or if you want to set up a new data space to share, you can skip this step and complete it later. However, your connection isn’t complete until you share at least one data space.
- Review the access that the connection grants between orgs. To approve the connection, click Connect.
When you create a Data 360 companion connection, a standard Salesforce CRM org connection is also created. If a Salesforce CRM connection to the org already exists, it's upgraded to a Data Cloud One companion connection with the same name.
- Tagging, Policies, and Access in Data Cloud One
Data Cloud One uses the same tagging, policy creation, and access management as the rest of Data 360, with added specifications. For both tagging and policy creation in Data Cloud One, the home org functions as a standalone org that can perform further syncing. - Objects Shared with Companion Orgs
Data model objects (DMOs) and calculated insights objects (CIOs) in shared data spaces are shared with the companion org. You can reference data from these objects with Data 360 features and use the data with platform features, such as Flow and related list enrichments. - Metadata Ownership in Connected Orgs
An object is owned by the org in which it originated, even when it's shared with Data 360 or from Data 360 to other connected orgs. You can only edit or delete data in the org that owns it. - Understand Data Spaces in Companion Orgs
Metadata is synced only between a Data 360 home org and its connected companion org when the metadata is part of a data space that is shared with the companion org. Metadata syncing enables companion orgs to reference data in Data 360 objects in shared data spaces.