Under Org Unit ID Field, type out or select the name of your Org Unit ID metadata name.Generate random Encryption key online with hash and Base64.Under Populate With Direct Reports, select No.Navigate to the Org Hierarchies section.Import your participants file by following the steps on the linked support page.Prepare a file of participants for a Skeleton hierarchy by following the directions on the linked support page. ![]() When the time comes to view data in the dashboards, managers can then view their teams’ data because the question has helped link the correct direct reports to the units of the organization to which they belong. For this reason, skeleton hierarchies are often paired with engagement surveys distributed via anonymous link.Īny engagement survey paired with a skeleton hierarchy should use the Org Hierarchy question type, so employees can identify the manager they belong to. In this design, you know exactly who your managers are, but do not know or necessarily want to include the identities of all of their direct reports. Skeleton hierarchies are different from other hierarchies because they are built around the managers in your company, not their direct reports. Any fields already being used as additional metadata for another hierarchy in your project will not show up in the field dropdown. You also cannot select fields that are already being used to configure other org hierarchies in your project. Qtip: You cannot select fields that are already being used for org hierarchy generation (e.g., ManagerID, EmployeeID). ![]() You can add multiple fields at a time by clicking the plus ( +) sign to the right of the field. Additional Metadata: If there are any other metadata that are unit-specific, add them here. ![]() In the example above, only participants from a certain hiring date are being included in the hierarchy.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |