|Please note: These Account Hierarchy User Guides are for our customers who have Account Hierarchy Management enabled. If your account is not yet using this feature, please refer to our Checkr Dashboard User Guides.|
Checkr Account Hierarchy Management allows you to structure your Checkr account to match your organization model. Checkr provides the tooling to define any number of `nodes`, in any parent-child configuration. These `nodes` are posted to your Checkr account using the Checkr API through the `hierarchy` endpoint, which allows you to update your account’s structure at any point in the development of your organization.
After you define your hierarchy, use it to structure Checkr’s features.
- You can assign Positive Adjudication Matrices (PAMs) and packages at the node level so that you can manage their application throughout your organization.
- Users’ roles and restrictions are also assigned to nodes so that you can control user roles by business unit.
- Checkr reports and invoices list nodes and parent nodes so that you can better analyze the rate and type of background checks that each business unit orders.
This functionality is available to all customers and will be the new Checkr standard after all existing accounts have transitioned to this new working model.
Work locations will be required for all accounts when ordering background checks from the Checkr Dashboard or through the Checkr APIs.
All other features of the Account Hierarchy Management model, (user restrictions, enhanced billing reporting, reusable packages and PAMs), are optional.
A hierarchy is a series of nodes that model an account and represent your organization's hiring and background check needs. You can define your hierarchies using either the Checkr Dashboard (for flat hierarchies with fewer than 150 nodes) or the Checkr APIs (for more complex structures).
Nodes are individual entities of the account hierarchy, as defined within Checkr. You can use the Checkr Dashboard to assign nodes to packages, PAMs, and users.
Work location is a city-state pair that defines where your candidate will be employed. State is required, and city is optional. To ensure more accurate compliance, Checkr recommends specifying both state and city.
Work location is a required field for all Checkr accounts when ordering a background check using the Dashboard or through the API. Work location is used both as a pointer for criminal searches and as a means to determine compliance needs.
Use the Checkr Dashboard to add a work location when issuing an invitation to your candidates.
When using the Checkr API to order background checks using the /invite or /report endpoints, a state is required and a city is optional.
Working with account hierarchies
Use the Checkr Dashboard to define simple hierarchies, assign adjudication matrices and packages to nodes, and assign users to nodes.
Define your hierarchy
Use the Account settings > Account Hierarchy page to build simple hierarchies of multiple nodes. Use the Checkr APIs to build hierarchies of greater than 150 nodes, or with parent-child relationships between nodes.
Assign nodes to packages
With the Account Hierarchy feature, packages are account-level objects and can have any number of assigned nodes. Use this feature to standardize and streamline the packages that your organization uses.
You can assign packages at any level of the hierarchy and endlessly reuse them in your account.
Child nodes can be assigned packages and inherit packages assigned to their parent.
You can manage packages only in the dashboard. Use the Packages page to assign nodes to packages.
Assign nodes to adjudication matrices
Adjudication matrices are account-level objects and can have any number of nodes assigned to them. You can use this function to standardize matrices across your organization.
You can assign adjudication matrices at any level of the hierarchy and endlessly reuse them in your account.
When ordering background checks, Checkr will apply the first adjudication matrix it encounters when stepping up the account hierarchy from the originating node. A background check ordered from a child node will use the child’s associated adjudication matrix, if one is available, even if its parent node is associated with a different matrix.
You can manage adjudication matrices only in the dashboard.
Grant user permissions
Users can be assigned to multiple nodes, which live on different branches or at different levels in your hierarchy. Assigning a user to a node grants them access to that node and to its children.
Checkr account admins can assign nodes to other users on the account. These users can then read reports only from the nodes they can access.
Users with notifications enabled receive notifications only from their assigned nodes.
Account admins can access all nodes in an account.
Admins can also assign nodes assigned to them to packages and PAMs.
Search and filter reports based on the node associated with the order (cost center), the node’s parents in the account hierarchy.
Add a work location when issuing an invitation to your candidates.
Refer to the Candidates page in these User Guides for more information.
Checkr invoices include two columns specific to Account Hierarchy Management: Cost Center and Hierarchy.
- Cost center is the name of the node associated with the background check.
- Hierarchy is a list of the cost center's parent, its parent’s parent, and all the way up the tree to a root node.
These two columns also appear in the Invoice Details CSV. Use these columns’ data to filter your invoices by any node or level of the hierarchy.