Edit

Share via

Business unit support and role-based access control (preview)

  • Article

[This article is prerelease documentation and is subject to change.]

Business unit support allows administrators to regulate access to customer profiles, segments, and measures based on business units. Learn more about business units and role-based access control in Dataverse.

Important

  • This is a preview feature.
  • Preview features aren't meant for production use and may have restricted functionality. These features are available before an official release so that customers can get early access and provide feedback.

Prerequisites

Note

  • Parent-child scope is currently not supported.
  • Modernized business units are not supported.
  • Field-level security is not supported.
  • It is not possible to disable business unit data separation on an environment after it has been enabled.

Access controls in Customer Insights - Data

Customer profiles, activities, customer measures, intelligence, enrichments

Access to a customer profile in Customer Insights - Data depends on the business unit team that owns the profile, the business unit team of the user, and the application permissions of the user. The Administrator, Contributor, and Viewer roles have access to all profiles regardless of the owning business unit team. The Marketing contributor role has access only to customer profiles that belong to their business unit.

The Marketing contributor role only has access to the customers, tables, segments, and measures views in the Customer Insights - Data user interface. The Marketing contributor role has a limited set of functionality. Learn more about user roles.

Note

The administrator and contributor roles are highly privileged and should only be given to users that belong to the Root business unit.The viewer role is not bound by business unit and should not be used in production if business unit data separation is enabled.

Ownership of the customer profiles is determined based on mappings that are configured on the Unify page:

  1. Go to Data > Unify > Business units
  2. Under Business unit data separation, select the column that identifies the business unit for each entity that contributes to unification. Unification rules can't be added on the selected columns.
  3. Under Associate customer profiles with business units, specify the mapping between the values in the selected columns and business unit teams. Only teams that have the Customer Insights Data Read Access role are available for selection. For example, 'A' maps to the business unit A team and 'B' maps to the business unit B team.

Screenshot of business unit mappings. Screenshot of business unit mapping.

Teams within business units (not business units directly) own customer profiles to provide better control of data access. Only one team per business unit can be specified in the mapping rules.

  • The system deduplicates and unifies profiles only if the business unit values match.
  • Profiles that don't match any of the mappings are assigned to the Org business unit.
  • All profiles are assigned to the Org business unit if business unit data separation isn't enabled.
  • A profile belongs to exactly one business unit.
  • The unification rules and customer profile schema are the same for all business units.

Note

Any changes to the business unit data separation configuration triggers a full refresh. If your data sources use incremental updates, a full refresh needs to be triggered manually after changes have been made.

Data relates to a customer profile, for example activities, inherit the business unit ownership from the associated profile.

Intelligence models are trained on all data, regardless of business unit data separation.

Default configurations

The following diagram shows a typical business unit structure. Marketing contributor users only have access to their business unit team's customer profiles. For example, if a marketing contributor user creates a segment with all customers, it only contains the customer profiles that map to the business unit of the segment owner.

Example of a business unit structure with the Org parent business unit at the top and child business units A to D. Example of a business unit structure with the Org parent business unit at the top and child business units A to D.

Segments and business measures

Segments and measures belong to the business unit of the user that created them. For example, if a user is a member of business unit A then any segment and measure that user creates belongs to business unit A. Access settings in Dataverse control access on the segment and measure definitions tables in Dataverse. By default, segments and measures are available to other users that belong to the same business unit.

Note

  • Segments and measures are owned by only one business unit and cannot be shared with other business units.
  • Only build your own segments and measures and no projected attributes are supported for the marketing contributor role.
  • For building segments and measures the Marketing contributor role only has access to Customer profiles, Unified activities, Segments, and Customer measures.

Next steps