Loading
About Salesforce Data 360
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Set Up a Data Cloud One Companion Connection

            You are here:

            1. Salesforce Help
            2. Docs
            3. Data 360

            Set Up a Data Cloud One Companion Connection

            Establish a bidirectional connection between Data 360 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
            To connect a Salesforce org

            System admin profile OR

            Data Cloud Architect permission set

            Make sure that users have the permissions to create companion connections. See Configure User Permissions for an External Salesforce Org Connection in Data 360 and Enable Object and Field Permissions to Access Salesforce CRM in Data 360.

            1. Plan your Data 360 architecture strategy.
              1. Review Data 360 Architecture Strategy for architectural considerations.
              2. Choose an org to be the Data 360 home org. Data 360 is provisioned on the home org.
              3. Choose orgs to be the companion orgs. You can't connect a companion org with Data 360 provisioned. If a potential companion org already has Data 360, you must first deprovision Data 360 on that org. See Convert a Data 360 Home Org to a Data Cloud One Companion Org.
              4. Configure the domain settings in the home org and companion orgs to ensure a successful connection.
                If you don't want users to log in to your org through your instanced URL, on the My Domain page in Setup, select Don’t redirect for your instanced URL in the redirections section.
                The Salesforce orgs that you’re connecting must have API access and allow access for the Salesforce IP range. See Salesforce IP Addresses and Domains to Allow
            2. Verify that the org you're connecting has a Data Cloud One Companion license. If not, add one using Your Account.
            3. From the Setup menu in the home org, select Data Cloud Setup.
            4. Select Data Cloud One, and click New.
              If you’ve reached your org’s maximum number of companion org connections, use Your Account on the home org to add a Data Cloud One Additional Connection license, and then try again.
            5. Log in to the Salesforce org that you want to connect as a Data 360 companion org.
            6. Review the org summary to confirm that you’re connecting to the correct org, and click Next.
            7. 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, data isn’t ingested or synced.
              Note
              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.
            8. 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 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.

            • 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 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.

            See Also

             
            Loading
            Salesforce Help | Article