How the Tagging System Works in Lever
Background checks can be triggered at any stage in the hiring process. You decide when during the hiring process (e.g., after the interview stage, before an offer is made) you want the background check to be triggered.
Once a candidate reaches the specified "trigger stage", the background check will automatically be triggered.
Tags are used to define which background check package is sent to the candidate. Each check package is assigned a unique tag that begins with ‘zinc_’. These tags are linked to specific check packages and determine which one will be sent when triggered.
If there is no tag assigned to a candidate or job, the default package (the first package in the list of packages) will be sent out.
Ways to Tag
There are two main ways to apply these tags:
1. Tagging the Job
This is the simplest way. If all candidates for a particular job require the same background check, you can tag the job itself. When a candidate moves to the trigger stage for that job, they'll automatically receive the correct background check.
2. Tagging the Candidate
This option gives you more flexibility. If different candidates for the same job need different background checks (for example, due to location), you can tag each candidate individually. Just make sure to tag the candidate before they reach the trigger stage. If you don't tag them in time, they'll receive the default background check package.
This option is especially helpful when dealing with global job postings that require different checks for candidates in different locations. By tagging candidates directly, you can assign the appropriate check package for their specific location.
How to Create a New Tag
Need a new tag for a new background check package? Here's how to get it done:
- Notify us of the new check package: Get in contact with your Account Manager or the Customer Success Team and let us know the name of the new check package you’ve created and the name you would like to be used on your tag.
- Tag creation: We will create the corresponding tag (beginning with ‘zinc_’) for your package.
- Tag assignment: You can then assign the tag either to the job or directly to the candidate to specify which checks should be triggered at the right stage.
Comments
0 comments
Please sign in to leave a comment.