|Available for||User roles||Super Admins, Admins, Team Members, Limited Team Members, Interviewers|
Please note: The Checkr integration needs to be set up by the Lever team. If you’re interested in using Lever’s integration with Checkr, please reach out to your point of contact, or contact support.
Before you can set up the Checkr integration to send candidates from Lever to Checkr, you need to reach out to your Lever point of contact or Lever’s support team. In your request, please provide:
- The name of the default package
- The name of the stage to trigger the initial background check (e.g. Background Check)
- (Optional) The name of the stage to advance the candidate to after a successful check
You’ll also need to send us your Checkr API key, but that will need to be sent securely.
Once that’s done, Lever will add the appropriate API key and webhook settings in your Lever account - do not delete these, or the integration will stop working!
Sending a candidate to Checkr
Once you’ve completed setup, any candidate who reaches your "trigger" stage will be sent to Checkr. Lever only sends the candidate name and email address to Checkr.
Once sent to Checkr, you'll be able to see the pending invite link on the homepage of the Checkr dashboard:
Once the candidate has been sent to Checkr, they will receive an invitation from Checkr via e-mail to begin the background check process. Once the invitation has been sent, Lever will add "Invitation Pending" tag to the candidate. Once they’ve completed the background check, the tag will change to "Invitation Completed". If there are no records, it will be changed to "Report Clear". If there is some sort of adverse action to evaluate (criminal records, traffic infractions, sex offender status, etc.), it will be changed to "Report Consider".
If the check returns "Report Clear", a gated link to the completed results will be added to the candidate profile in the links section - only authenticated Checkr users will be able to access it.
Override your Default Package
During setup, we’ll ask for a default package to send to all users. We do, however, understand that for a variety of reasons you might have different background checks for different roles or candidates.
Say you wanted your "Account Executive" position to trigger a special AE-specific package, but your default is something else. In Checkr, there will be a predefined "slug" for each package that will override the default. A candidate who reaches the "trigger" background stage with one of these unique tags will be sent the override package instead of the default. The slug is typically the name of the package, but in all lowercase and with underscores instead of spaces. Additionally, we require adding the prefix "bc_" in order to differentiate tags that are associated with the Checkr integration ("bc_" stands for Background Checkr). For example, if you wanted to override the default package and use the package "New Hire", you would tag the candidate with "bc_new_hire". Check the slugs in your Checkr account to make sure you're properly tagging candidates!
Tip: Add posting specific tags to candidate profiles by adding a tag to the posting. If you add a tag to your posting, all candidates that apply to the posting will receive that tag. More information on configuring tags here.