The Hierarchy Manager implementer is responsible for designing and setting up the hierarchies, entity types and relationship types. The Implementer then defines one or more Hierarchy Manager profiles, which describe what fields and records Hierarchy Manager users may display, edit, or add. For example, there can be one profile that allows full read and write access to all entities and relationships and another profile that is

read-only

(no add or edit operations allowed).

Another situation where you might use a profile is where a user may be allowed to access certain relationship types but not others. For example, you have two relationship types,

Org-Customer

and

Org-Org

. One user may have access to both these relationship types but another user may only have access to Org-Org Rel type.

Hierarchy Manager profiles are assigned to users through MDM Hub roles. If a user ends up having access to multiple Hierarchy Manager profiles through MDM Hub roles, the user is prompted at the appropriate time to select the profile with which to work. Users specify which profile they want to use when the Hierarchy Manager starts.