You are here:
Ingest Hierarchical Data
Bring Salesforce CRM organizational hierarchies such as Role, Manager, and Territory into Data 360. After ingestion, you can reference these hierarchies in hierarchy-based record-level security (RLS) policies.
Required Editions
| Available in: All Editions supported by Data 360. See Data 360 edition availability. |
| User Permissions Needed | |
|---|---|
| To access Data 360 Setup: | Permission set:
|
Before completing this task, consider these guidelines and limitations.
- Hierarchy data is synchronized periodically. It can take up to 15 minutes for changes in the source system to be reflected in Data 360.
- For the hierarchy operator to appear as an option in Policy Builder, complete the hierarchy setup.
- After you configure a hierarchy, you can’t edit or delete it.
- To use RLS hierarchy, install the required version of the Salesforce Standard Data Model
SSOT package in your org. Hierarchy ingestion fails if the required version isn't installed.
- Role hierarchy requires SSOT version 1.83 or later, which includes the
ssot_UserRole__dlmobject. - Manager hierarchy requires SSOT version 1.116 or later, which introduces the
ManagerId__cfield in thessot_User_dlmobject. - If you use both Role and Manager hierarchy, install SSOT version 1.116 or later.
- Role hierarchy requires SSOT version 1.83 or later, which includes the
To configure hierarchy ingestion:
- Go to Data Cloud Setup.
- From Quick Find, search for and select Hierarchy Ingestion.
- On the Hierarchy Ingestion page, click New Hierarchy Ingestion.
-
From the Source Connection dropdown menu, select the connector for the core org that you
want to ingest hierarchy data from.
One data lake object (DLO) is created for each connection, and all DLOs in a hierarchy are mapped to a single data model object (DMO) within each data space.
- For a Role hierarchy, two DLOs are created: UserRole and User.
- For a Manager hierarchy, one DLO is created: User.
- For a territory hierarchy, three DLOs are created: User, Territory2, and UserTerritory2Association.
-
From the Hierarchy dropdown menu, select the hierarchy to ingest. For example,
Role.
Currently, only Role, Manager, and Territory hierarchies are supported. When you set up a hierarchy, Data 360 automatically creates hierarchy data objects. You can secure these hierarchy objects independently, similar to other DLOs and DMOs.
- From the Data Space dropdown menu, select the corresponding data space for this hierarchy. For example, AMER or EMEA.
- (Optional) To add additional hierarchies, click +Add Hierarchy.
- Save your configuration.
Did this article solve your issue?
Let us know so we can improve!

