Hierarchies define the way in which portal users receive relevant information. Hierarchies that are based on the default template have only one level.
Hierarchies that are based on the classic template have multiple levels, and you can expand and collapse groups.
From a technical perspective, a hierarchy always has a tree structure and is level-based. A level can be made up of models, objects, or groups. It may contain a superior item and multiple subordinate items. In contrast, a level can have multiple subordinate items.
You can use multiple hierarchy definitions in a hierarchy configuration. For example, you can specify the following hierarchy definitions in a configuration:
Navigation in process models (value-added chain diagrams, EPCs, and function allocation diagrams), navigation in the organization (organizational charts, organizational units, roles, and groups), and navigation in the IT systems within an organization.