📄️ About Dynamic Hierarchies
Dynamic Hierarchies in EmpowerID automate the lifecycle management of data-driven, nested groups within your organization. By leveraging authoritative enterprise data, EmpowerID's Dynamic Hierarchies engine enables the creation, updating, and removal of groups in systems like Active Directory and Azure Active Directory, without requiring manual intervention.
📄️ Dynamic Hierarchy Policy for Person Attribute Management Roles
You can use a Dynamic Hierarchy policy to automatically generate Management Roles and assign people to those roles based on the value of a specified attribute, such as the name of their department. After the policy is created, the Dynamic Hierarchy engine will add any person with the matching attribute value to the Management Role.
📄️ One-Level Dual Attributes
EmpowerID provides the capability for you to create Dynamic Hierarchy policies that allow groups to be dynamically generated based on the value of any two specified Person attributes, such as the State and City attributes. When the policy runs, EmpowerID creates a group for the specified attributes. EmpowerID then places any Person accounts with those matching attributes in the group.
📄️ 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.
📄️ Two-Level Management Roles
EmpowerID provides the capability for you to create Dynamic Hierarchy policies that provision Management Roles and Management Role Definitions based on the value of two specified Person attributes, such as Title and City. When these types of policies first run, EmpowerID provisions the Management Role Definition based on the first level attribute chosen and the Management Role, based on a combination of the first and second level attributes selected. After the parent Management Role Definitions and Management Roles are provisioned, Persons with attributes matching the two specified attributes is added to the Management Roles.
📄️ Use Dynamic Hierarchy Policies to Create External Roles and Locations
You can use a Dynamic Hierarchy policy to automatically generate external Business Roles and Locations based on the value of a specified person attribute, such as the name of their department. After the policy is created, the Dynamic Hierarchy engine will add any person with the matching attribute values to the Role and Location.
📄️ Use Dynamic Hierarchy Policies to Create One-Level Triple Attributes Groups
EmpowerID provides the capability for you to create Dynamic Hierarchy policies that allow groups to be dynamically generated based on the value of any three specified Person attributes, such as the State, City, and Country attributes. When the policy runs, EmpowerID creates a group for the specified attributes. EmpowerID then places any Person accounts with those matching attributes in the group.
📄️ Use Dynamic Hierarchy Policies to Create Two-Level Attribute Nested Groups
EmpowerID provides the capability for you to create Dynamic Hierarchy policies that allow nested groups to be dynamically generated based on the value of any two specified Person attributes, such as the State and City attributes. When the policy runs, EmpowerID creates a top-level group for the first attribute specified and a nested group under that top-level group for the second attribute specified. EmpowerID then places any Person accounts with those matching attributes in those groups, depending on how you configure the policy. You can configure the policy to place people in both the top-level and nested groups or only in the nested group. In addition, you can configure the policy to create top-level groups only if the condition for the nested group exists.