|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 business 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 business.
Once your hierarchy is defined, use it to structure Checkr’s features.
- PAMs and Packages may be assigned at the node level, allowing you to manage their application throughout your business.
- Users’ roles and restrictions are also assigned to nodes, allowing you to control user roles by business unit.
- Nodes and their parent nodes are listed on Checkr Reports and Invoices, allowing you to better analyze the rate and type of background checks ordered by business unit.
This functionality is available to all customers, and will be the new Checkr standard after all existing accounts have been 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 the customer’s business with respect to their hiring and BGC needs. Customers may define their 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. Nodes can be assigned to Packages, PAMs, and Users using the Checkr Dashboard.
Work location is a city-state pair that defines where your candidate will be employed. State is required; city is optional. We recommend that both be included when initiating new background checks to ensure more accurate compliance.
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.
State is also required and City optional when using the Checkr API to order background checks using the /invite or /report endpoints.
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 Account Hierarchy, Packages are account-level objects and can have any number of Nodes assigned to them. Use this feature to standardize and streamline the Packages used across your organization.
Packages can be assigned at any level of the hierarchy and can be endlessly reused within an account.
Child nodes may be assigned Packages, and will inherit any Packages assigned to their parent.
Packages can be managed only in the Dashboard. Use the Home page to assign Nodes to Packages.
Assign Nodes to Adjudication Matrices
Adjudication Matrices are account-level objects and may have any number of nodes assigned to them. This can be used to help you standardize your Matrices across your organization.
Adjudication Matrices can be assigned at any level of the hierarchy and can be endlessly reused within an 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.
Adjudication Matrices can be managed only in the Dashboard.
Grant User permissions
Users may be assigned to multiple nodes, which may 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 may assign nodes to other users on the account. These users will then be restricted to seeing only Reports from the nodes to which they have access.
Users with notifications enabled will only receive notifications from their assigned nodes.
Account Admins have access to all nodes within an account.
Admins may 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.
See 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 until a root node is reached.
These two columns are also present in the Invoice Details CSV. Use these columns’ data to filter your invoices by any node or level of the hierarchy.