Hierarchy allows you to define sets of hierarchical relationships between users, locations, etc. based this profile field type.
You can -for example- use Hierarchy to define a relationship between assorted titles like this:
President → Regional Director → General Manager → Assistant Manager → Floor Worker
Or based on location like this:
Planet → Country → State → County → City
You can then use the Rules Engine to set permissions based on where in your organization a user sits. If all users in California have a certain compliance training, you can create an enrollment for this training with an audience of:
Location Hierarchy [is equal to or below] California.
Another use for it would be to ensure that all management of a certain level or higher takes a Responsibilities of Management training. After you have defined your hierarchy structure, this is is as simple as creating a rule like:
Title [is above] General Manager.
Hierarchy Technical Details
- Node: each record in the hierarchy.
- Depth: number of layers in the hierarchy.
User Profile and Rule Changes
If a node is removed:
- The node will be removed from any user profile with it set.
- Any rules containing that node will be removed.
If a node is moved:
- Any users with that node set in their user profile will effectively move with that node – it will stay attached to their profile.
- Those users may see changes in access granted or removed based on the new position in the hierarchy.
Limitations - Hierarchy in General
- A user's place on the hierarchy cannot be changed from the learner side.
- The field is not user editable.
- The field cannot be placed on a welcome or registration page.
- There is a recommended maximum of 5,000 nodes.
- There is a hard maximum depth of 10.