Skip to main content
  • Customer Experience
    Customer Experience
  • Employee Experience
    Employee Experience
  • Brand Experience
    Brand Experience
  • Product Experience
    Product Experience
  • Core XM
    Core XM
  • Design XM
    Design XM

Generating a Level-Based Hierarchy (EE)

What's on This Page:

Was this helpful?

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

The feedback you submit here is used only to help improve this page.

That’s great! Thank you for your feedback!

Thank you for your feedback!

Qtip: This page describes functionality available to Engagement projects, but not Lifecycle or Ad Hoc Employee Research projects. For more details on each, see Types of Employee Experience Projects.

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.

Qtip: Not sure what type of hierarchy fits your HR data best? Check out a basic comparison of your options on the Hierarchies Basic Overview page.

Generating a Level-Based Hierarchy

Warning: You may have up to 10 hierarchies in a project. Once you reach 7 hierarchies, you will receive a warning that you’re approaching the hierarchy limit. If you have 10 hierarchies, you will not be able to create another without deleting a 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.
    navigating to the org hierarchy tab and clicking create a hierarchy
  4. Navigate to the Org Hierarchies section.
  5. Click Create Org Hierarchy.
  6. Type a Name for your hierarchy.
    The Create New Hierarchy window
  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. Under Organizational Levels, select the metadata field where you define your first level. For example, we simply call our first level “Level 1.”
  11. 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.”
     In the Organization Levels fields, Level 1 is set equal to 1, and Level 2 is set equal to 2
  12. Click the plus (+) sign to add another level.
  13. Select the metadata field where you define your second level. For example, we simply call our second level “Level 2.”
  14. If you’re assigning managers, select the value that indicates someone is a manager in this level.
  15. Add additional levels and manager values as needed.
  16. When all of your levels have been added, click Create.

Other Options for Generating a Level-Based Hierarchy

Use Org Unit ID

If you have Org Unit IDs uploaded with your participants, you can incorporate this into your Level-Based hierarchy. 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.

Use Org Unit ID is enabled, creating an extra field in each row of the Organizational Levels section named Org Unit ID

  1. Turn the Use Org Unit ID setting On.
  2. When defining your Organizational Levels, select the metadata where you saved Org Unit ID.
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.

Limit People Included

Turn the Limit People Included setting On to restrict what participants are included in the hierarchy based on additional metadata you uploaded with your participants. In the example below, only participants from a certain country are included in the hierarchy.

Limit People Included is enabled, creating fields where you can specify metadata fields and values that you limit people by