The Hierarchy screen lets you administer user access rights so that they match your organizational structure. In addition, you can use the hierarchy to view or edit details about vehicles and fleets, and to configure the dashboard.
The hierarchy is made up of nodes, where each node represents access to information about a specific fleet of vehicles and a specific team of drivers. Typically, the nodes in the hierarchy correspond to an area, location, or position within your organization.
Drivers and (typically, but varying according to account configuration) vehicles are assigned to the nodes at the lowest level of the hierarchy. For any node in the hierarchy, the associated fleet is the set of all vehicles belonging to nodes within and below it. Similarly, the team associated with any node in the hierarchy is the set of all drivers belonging to nodes lower in the hierarchy. This is illustrated in the following figure:
Drivers are assigned to the nodes at the lowest level (shown in a darker color). Vehicles are also typically assigned to the lowest node level, unless your account has been configured to allow them to be assigned to higher nodes. The team and fleet associated with nodes at the higher levels are the sum of all drivers and vehicles associated with lower nodes. For best performance, a node in the hierarchy should not be associated with a fleet of more than 500 vehicles.
Unlike fleets and teams that are created from the Fleets & Teams screen, fleets and teams associated with a node in the hierarchy cannot be edited outside of the hierarchy.
A hierarchy node also has an associated set of users, which are assigned directly to the node. The users associated with a node cannot access information about any fleets or teams associated with nodes that are not below them in the hierarchy. Similarly, users can only access details about users associated with nodes lower in the hierarchy.
Finally, hierarchy nodes have an associated set of roles, which are assigned directly to the node. When a role is assigned to a hierarchy node, it has access to information about any fleets or teams associated with that node or any of the nodes under it (similar to the permissions granted to users assigned to a node). By assigning roles that have been added to a hierarchy node to a user, you can grant that user permission to view portions of the hierarchy that are not located below that user's node.
The hierarchy has a single root node. Typically, the main user for an organization is assigned to this root node (although it is possible for a hierarchy to span multiple accounts that share vehicles or drivers, or both). Any user that is assigned to a node in the hierarchy can only see the portion of the hierarchy at or below that node. Thus, all users see the hierarchy as rooted at their own nodes.
All the drivers or vehicles assigned to a given node in the hierarchy share the same settings. By default, every node in the hierarchy inherits the settings of its parent node. This inheritance makes it easy to change the settings for all vehicles or drivers in an organization by changing the settings of the root node in the hierarchy. You can override the inherited settings for a driver or vehicle by editing the driver or vehicle directly.