Hierarchy Developer's Guide for Oracle Self-Service E-Billing > Hierarchy Manager Concepts >

Hierarchy Role-Based Access Control

Hierarchy Manager supports both hierarchy-based and role-based access control.

• Hierarchy-Based Access Control. A user is assigned or associated with one of the nodes inside Hierarchy Manager. Once it is assigned, the user has granted access to all the nodes under the assigned node, as shown in the following diagram:

A user may be assigned to one or multiple nodes in the same hierarchy as long as these nodes are not on the same path to the root node.

• Hierarchy Role-Based Access Control. Hierarchy Manager supports the following roles:
  • Subscriber. Users with this role can see assigned hierarchies, including all nodes from assigned node down. View assigned hierarchy only. No editing or assignment allowed. Users with this type of role need to be assigned or associated with a node in order to access the hierarchy.
  • Manager. User with this role can see assigned hierarchies, including all nodes from assigned node down. They can create, view, edit, and delete hierarchies, and assign or un-assign other Managers and Subscribers to and from sub tree. Users with this type of role must assigned or associated with a node in order to access the hierarchy.
  • System Administrator. Users with this role can see hierarchies within their company, including all nodes in the hierarchy. They can create, view, edit, and delete hierarchies and assign Managers and Subscribers. Users with this type of role do not need to be assigned or associated with any hierarchy tree node in order to see the hierarchy.
  • Customer Service Representative (CSR). Users with this role can see all hierarchies in across companies, starting from root node. They can create and delete hierarchies. By default, the Hierarchy Manager UI does not support this feature yet. However, the provided API allows you custom implementation of this role.