Multi-Org Account Configuration in Marketing Cloud Connect

Multi-Org is an Enterprise 2.0 account configuration. This configuration allows individual Marketing Cloud Engagement business units to connect with a single Salesforce org, independent of the parent account or other business units. Using Marketing Cloud Connect for Marketing Cloud Engagement, this configuration includes two setup scenarios.

Important Multi-org configuration isn’t compatible with Government Cloud. Government Cloud accounts require a 1:1 relationship.

• Multiple business units connected to multiple orgs.

  We support up to 5 business units to the same Salesforce system user in a multi-org environment. If you use more than 5 business units, service can be degraded and can negatively impact the servers. If you must connect more than 5 business units, designate additional system users.

• Multiple business units connected to a single org.

Multi-Org is available for Enterprise 2.0 accounts. It requires Connected App Authentication and Custom Profile Centers. Not sure what type of account you have? Review Engagement editions for more information.

These best practices are recommended when configuring multi-org.

• Control access to the All Subscribers list.

  The All Subscribers list is a comprehensive list of all subscribers, even in a multi-org account. To prevent users from seeing subscribers outside of an org they can access, remove non-admin users’ access to All Subscribers and use Subscriber Business Unit Filters.

• Plan your business unit and user connections.

  While disconnecting accounts is supported, plan your Salesforce org to Engagement business unit and user connections carefully before implementation.

• Use dedicated API users.

  Assign each connected business unit a dedicated API user to reduce confusion after connecting. If multiple business units are connected to the same Salesforce org, use a shared API User.

Warning If you use Synchronized Data Sources with multi-org configuration, when you disconnect a business unit from Sales or Service Cloud, synchronized data extension names can change. To ensure that they continue working, update query activities that reference those synchronized data extensions.