Generating a Level-Based Hierarchy (EE)

About Level-Based Hierarchies

Level-Based hierarchies are a good option if your HR data includes each level the employee reports to, from the top of the hierarchy all the way down to where the employee sits. With Level-Based hierarchies, you don’t necessarily have to know who the employee’s manager is; you just need to know the chain of command for each employee you’re including in the project. This data format is often more common with companies that organize employee data by distinct levels, location, or functional breakout.

Generating a Level-Based Hierarchy

1. Prepare a file of participants for a Level-Based hierarchy by following the directions on the linked support page.
2. Import your participants file by following the steps on the linked support page.
3. Navigate to the Participants tab.
   
4. Navigate to the Org Hierarchies section.
5. Click Create Org Hierarchy.
6. Type a Name for your hierarchy.
   
7. Under Type, select Level-Based.
8. If you want your units to have managers, turn Assign Managers to On.
9. Under Manager Type Field, select the metadata field where you indicate the managers in your hierarchy.
10. If you have Org Unit IDs uploaded with your participants, turn the Use Org Unit ID setting On.
    Qtip: When you use Org Unit IDs, you do not have to manually map your hierarchy units from other projects so you can compare data across projects in your dashboards; instead, units with the same ID will be recognized as the same, even if their names have changed.
    Qtip: There must be one Org Unit ID column for each level in the Level-Based hierarchy. For example, if your organization has two levels, “Level 1” and “Level 2”, then you will need two columns for Org Unit IDs: “Org Unit ID 1”, which contains the Org Unit ID for anyone in Level 1, and “Org Unit ID 2”, which contains the Org Unit ID for anyone in Level 2.
11. Under Organizational Levels, select the metadata field where you define your first level. For example, we simply call our first level “Level 1.”
    Qtip: If you turned on Use Org Unit ID, select the metadata where you saved Org Unit ID.
12. If you’re assigning managers, select the value that indicates someone is a manager in this level. In this example, we indicated managers with the value “Yes.” This was the same for all level columns.
    Qtip: If you chose a Manager Level style metadata instead, your levels may look more like the example image below, where managers at Level 1 have the value “1,” and managers at Level 2 have the value “2.”
     
13. Click the plus (+) sign to add another level.
14. Select the metadata field where you define your second level. For example, we simply call our second level “Level 2.”
15. If you’re assigning managers, select the value that indicates someone is a manager in this level.
16. Add additional levels and manager values as needed.
17. If you’d like, select Show Advanced Options. See the section below for more details.
18. When all of your levels have been added, click Create.

Advanced Options

If you click Advanced Options, you will have several additional options when building your Level-Based hierarchy.

• Limit people: If you would like to limit the people included in the hierarchy based off of a metadata value, turn this option On. In the example above, only participants from a certain hiring date are being included in the hierarchy.
• Additional metadata: If there are any other metadata that are unit-specific, add them here. You can add multiple fields at a time by clicking the plus (+) sign to the right of the field.
  Qtip: You cannot select fields that are already being used for org hierarchy generation (e.g., ManagerID, EmployeeID). You also cannot select fields that are already being used to configure other org hierarchies in your project. Any fields already being used as additional metadata for another hierarchy in your project will not show up in the field dropdown.

FAQs