---
schema_version: "1"
id: 61c8a987ab03d8f457f3b8267b922c6149bb110bfcb3775e39c11a265b8cfd16
title: Ingest Hierarchical Data
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_ingest_hierarchy_data.md
canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_ingest_hierarchy_data.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: d44c927d6407261b3c65d41b70b56a701ce0f406877b6fa90077ac58b99831d3
description: 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.
products:
  - Data 360
release: "264"
---
# 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

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>All Editions</strong> supported by Data 360. See <a href="https://help.salesforce.com/s/articleView?id=data.c360_a_dc_editions.htm&amp;release=264.0.0&amp;type=5" title="Data 360 is available in several supported Salesforce editions. Some Data 360 features also require additional licenses.">Data 360 edition availability</a>.</td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col>
          <col>
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:left;vertical-align:top;" id="d99258e69">User Permissions Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d99258e69 ">To access Data 360 Setup:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d99258e69 ">
              <p>Permission set: </p>
              <ul>
                <li>Data Cloud Admin</li>

              </ul>
            </td>

          </tr>
        </tbody>
      </table>

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__dlm` object.
    - Manager hierarchy requires SSOT version 1.116 or later, which introduces the `ManagerId__c` field in the `ssot_User_dlm` object.
    - If you use both Role and Manager hierarchy, install SSOT version 1.116 or later.

To configure hierarchy ingestion:

1. Go to **Data Cloud Setup**.
2. From Quick Find, search for and select **Hierarchy Ingestion**.
3. On the Hierarchy Ingestion page, click **New Hierarchy Ingestion**.
4. From the Source Connection dropdown menu, select the connector for your Salesforce 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.
5. 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.
6. From the Data Space dropdown menu, select the corresponding data space for this hierarchy. For example, **AMER** or **EMEA**.
7. (Optional) To add additional hierarchies, click **+Add Hierarchy**.
8. **Save** your configuration.