Business Support

Understanding hierarchy concepts and terms

In both Bill Analyst and Usage Analyst you can use hierarchies to organize spending, allocate costs, and report on telecom costs and use. You'll want to set up hierarchies to reflect the organization of your company—multiple regional offices, retail outlet chains, cooperatives, departments, etc.

Create hierarchies in the same way you would organize your documents in Microsoft File Explorer with files, folders, and documents. Hierarchies are made up of individual nodes. You can create as many nodes or sub nodes as needed. Accounts are assigned at the node level. Services are assigned at the account level. After you build a custom hierarchy, you can use it every month to allocate costs across your organization in just seconds.

Note: Hierarchies and their levels also work as filters when running summary and detail reports.

These four hierarchy concepts are important for you to know about: 
 

  1. Set hierarchy—is used to create new hierarchies, change hierarchy names, and view hierarchy attributes (e.g., active, master). It's restricted based on permission level.

  2. Active hierarchy—after you create a new hierarchy, it becomes the active hierarchy. Only one hierarchy is active at a time. Any changes to nodes, account assignments, and service assignments only affect the active hierarchy. When there's more than one hierarchy, the active hierarchy is displayed on pages in the hierarchy section and in the reporting bar of summary and detail reports. Administrative users, or users assigned to the top node, can change which hierarchy is the active hierarchy.

  3. Public and private hierarchies—is a designation you assign a hierarchy. Public hierarchies can be accessed by any users who have access to the root node of the master hierarchy. Private hierarchies can only be seen by you. They can be changed to public at any time, but after a hierarchy is made public, it cannot be changed back to private.

  4. Master hierarchy—only a public hierarchy can be set to be the master hierarchy. If you change the master hierarchy, it will unassign all users not assigned to the top node since users are assigned access rights to branches of the master hierarchy. Unassigned users will have to be reassigned to the nodes of the new master hierarchy.

Did you know? You can watch our video on how to create and use hierarchies in Bill Analyst to learn more. They work the same way in Usage Analyst.