Organization Chart Groups

EmpowerID provides the capability for you to create Dynamic Hierarchy policies that allow groups to be dynamically generated based on organizational management hierarchies. The groups generated by the Dynamic Hierarchy policy can be based either on EmpowerID Person relationships or on the ManagerPersonID value defined within a connected directory. Groups are created in a selected organizational unit for each manager and direct report accounts are added as members of those groups.

In this topic, we demonstrate creating an Organization Chart Groups Dynamic Hierarchy policy based on EmpowerID Person relationship.

The Extension Attribute 1 and Extension Attribute 2 values for each group created by a Dynamic Hierarchy policy are internally managed by EmpowerID and should not be altered.

To create an Organization Chart Dynamic Hierarchy Policy

  1. In the Navigation Sidebar of the EmpowerID Web interface, expand Admin, then Policies, and click Dynamic Hierarchies.
  2. From the Dynamic Hierarchies find page, click the Add (+) button.



  3. In the Choose Type section of the Policy Details form that appears, select Organization Chart Groups from the Select a Policy Type drop-down.
  4. In the General section of the Policy Details form, do the following:
    1. Type a name and description for the policy in the Name and Description fields, respectively.
    2. Select the appropriate account store from the Directory drop-down.

  5. In the Hierarchy Generation section of the Policy Details form, do the following:
    1. Select Hierarchy Generation Enabled so that the option is enabled. Doing so allows EmpowerID to generate the dynamic group hierarchies.
    2. Click the Hierarchy Generation Next Run field and in the calendar control that appears, specify the date and time for the next run of the Hierarchy Generation job.
    3. Optionally, underneath Hierarchy Generation Schedule, click the Start and End fields and in the calendar control that appears for each field, specify the respective start and end dates for hierarchy generation to occur.

      The default values for these fields is a start schedule of one day before the current day and an end date of 97 years from the start date. If you change these values, set the Start date to one day before the date specified in the Hierarchy Generation Next Run field to ensure the generation occurs as expected.

    4. Specify the occurrence interval for the hierarchy generation from the Interval pane. When doing so, you have the following options:
      • Once - Hierarchy generation occurs one time.
      • Minute Interval - Hierarchy generation occurs "X" times every "Y" minutes as specified in the Run Indefinitely, Iterations and Interval fields. So, for example, if you select an iteration of 2 and an interval of 24, hierarchy generation will occur twice. The first occurrence is at the date and time specified in the Hierarchy Generation Next Run field and the second occurrence is 24 minutes after the first run completes. However, if you select Run Indefinitely, and then select an Interval of 24, hierarchy generation will once every 24 minutes, indefinitely.
      • Hour Interval - Hierarchy generation occurs "X" times every "Y" hours as specified in the Run Indefinitely, Iterations and Interval fields. So, for example, if you select an iteration of 2 and an interval of 24, hierarchy generation will occur twice. The first occurrence is at the date and time specified in the Hierarchy Generation Next Run field and the second occurrence is 24 hours after the first run completes. However, if you select Run Indefinitely, and then select an Interval of 24, hierarchy generation will once every 24 hours, indefinitely.
      • Daily - Hierarchy generation occurs once every "X" days at a designated time as specified in the Run Indefinitely, Iterations and Times fields. So, for example, if you select an iteration of 2, hierarchy generation will occur twice. The first occurrence is at the date and time specified in the Hierarchy Generation Next Run field and the second occurrence is on the following day at the time specified in the Times field. However, if you select Run Indefinitely, hierarchy generation will occur on a daily basis at the time specified in the Times field.

  6. In the Membership Recalculation section of the Policy Details form, do the following:
    1. Select Membership Recalculation Enabled so that the option is enabled. Doing so allows EmpowerID to update group membership as specified.
    2. Click the Membership Recalculate Next Run field and in the calendar control that appears, specify the date and time for the next run of the Dynamic Hierarchy Membership Recalculation job.

    3. Optionally, underneath Membership Recalculation Schedule, click the Start and End fields and in the calendar control that appears for each field, specify the respective start and end dates for hierarchy generation to occur.

      The default values for these fields is a start schedule of one day before the current day and an end date of 97 years from the start date. If you change these values, set the Start date to one day before the date specified in the Membership Recalculate Next Run field to ensure the generation occurs as expected.

    4. Specify the occurrence interval for the hierarchy generation from the Interval pane. When doing so, you have the following options:
      • Once - Membership recalculation occurs one time.
      • Minute Interval - Membership recalculation occurs "X" times every "Y" minutes as specified in the Run Indefinitely, Iterations and Interval fields. So, for example, if you select an iteration of 2 and an interval of 24, membership recalculation will occur twice. The first occurrence is at the date and time specified in the Membership Recalculate Next Run field and the second occurrence is 24 minutes after the first run completes. However, if you select Run Indefinitely, and then select an Interval of 24, membership recalculation will once every 24 minutes, indefinitely.
      • Hour Interval - Membership recalculation occurs "X" times every "Y" hours as specified in the Run Indefinitely, Iterations and Interval fields. So, for example, if you select an iteration of 2 and an interval of 24, membership recalculation will occur twice. The first occurrence is at the date and time specified in the Membership Recalculate Next Run field and the second occurrence is 24 hours after the first run completes. However, if you select Run Indefinitely, and then select an Interval of 24, membership recalculation will once every 24 hours, indefinitely.
      • Daily - Membership recalculation occurs once every "X" days at a designated time as specified in the Run Indefinitely, Iterations and Times fields. So, for example, if you select an iteration of 2, membership recalculation will occur twice. The first occurrence is at the date and time specified in the Membership Recalculation Next Run field and the second occurrence is on the following day at the time specified in the Times field. However, if you select Run Indefinitely, membership recalculation will occur on a daily basis at the time specified in the Times field.

  7. In the Policy Settings section of the Create Dynamic Hierarchy Policy form, do the following:
    1. Select Use EmpowerID Person Relationship data. This tells EmpowerID to generate one Direct Reports group for each manager relationship in EmpowerID, populating the membership of each with users whom the manager manages.
    2. Select whether to Nest Manager Groups. This allows you to nest groups for each cascading direct reports.
    3. Select whether to Mail-Enable Groups. Please note that Exchange is required for this feature.
    4. Select the appropriate action for EmpowerID to take if a group is empty from the Empty Group Action drop-down.
    5. Select the type of group you wish EmpowerID to create from the Group Type drop-down.
    6. Underneath Group Creation Location, click Select an OU and then select the OU where EmpowerID provisions the dynamically generated groups.

      After completing the above, the Policy Settings section of the form looks similar to the following image:



  8. In the Alerts section, select or deselect Alerts based on the action taken:
    • Create OU Alert Active - Select this box if you wish an alert to be sent when an OU is created, based on the dynamic group hierarchy policy settings.
    • Create OU Alert - Search for and select the alert to be sent when an OUis created by the policy.
    • Create Group Alert Active - Select this box if you wish an alert to be sent when a group is created, based on the dynamic group hierarchy policy settings.
    • Create Group Alert - Search for and select the alert to be sent when a group is created by the policy.
    • Delete Group Alert Active - Select this box if you wish an alert to be sent when a group is deleted, based on the dynamic group hierarchy policy settings. The specific setting that governs whether or not a group is automatically deleted is theEmpty Group Action setting. If that field is set toDelete, the only time a dynamic group is deleted is when there are no members in the group.
    • Delete Group Alert - Search for and select the alert to be sent when a group that was created by the policy is deleted by the policy.
    • Membership Change Alert Active - Select this box if you wish an alert to be sent when the membership of the dynamic group hierarchy changes.
    • Membership Change Alert - Search for and select the alert to be sent when the membership of a group created by the policy changes.

  9. Click Save.


After the Dynamic Hierarchy Policy runs, you can see the new groups provisioned by the policy in a Group search. You can also view the Dynamic Hierarchy Membership Inbox and Dynamic Hierarchy Provision Inbox by expanding System Logs and clicking Dynamic Hierarchy Inbox on the Navigation Sidebar. 




You can view the people who have been dynamically added to the group by clicking on the Display Name link for that group and expanding the Resultant Members accordion on the View One page for the group that appears. Additionally, you can view any nested group members by expanding the Nested Group Members accordion.


Related Content