1. Click Connect in the Lever Integrations Page to login to Lever
   

1. Select the stage from which the candidate will be retrieved from Lever to SpringVerify.
   
1. If you want the candidate exported when marked as “Hired”, you can leave this field as “Select Stage”.
   

---

1. Next, configure the background check package applied to a candidate by mapping the appropriate tag from Lever
   
1. NOTE: Each candidate on a Lever must have a tag associated in order to select the right package. If a candidate is detected without a tag or unmapped tags, that candidate will not be added to SpringVerify
   

1. Instead of having to add a tag to every candidate, which can sometimes lead to the user forgetting to add the tag, it is recommended to add the relevant tag to the job opportunity

2. This will ensure that every candidate applying for an opportunity will automatically have the relevant tag added to their profile without having to add it manually

Need to set a default package for all candidates without using a tag?

• If you use only one package variant for all your candidates and don’t want to have to add a tag for every candidate, contact cs@springverify.com

How does the integration work?

1. SpringVerify will check Lever every 15m to identify new candidates that are in the stage configured by you

2. If candidates are found with the following mandatory information, then they will be added successfully to SpringVerify

1. Name

2. Email

3. Phone

4. Tag (to select the correct package on SpringVerify)

Potential issues with the integration and how to handle them

In the event something goes wrong, SpringVerify Admins will receive an email detailing the problem. Common issues:

1. Candidates without the required information

1. Fix by ensuring every candidate include the required information on Lever

2. Re-add these candidate manually on SpringVerify

2. Candidate with unmapped tags or no tags

1. Fix by ensuring every candidate has the correct tag

3. Authentication Issue

1. The user who set up this integration may have revoked access to SpringVerify or might have their account deleted

2. Fix by visiting SpringVerify and re-authenticating by starting from Step 1

4. Stage not found

1. The stage configured is no longer available as it might have been deleted on Lever

2. Fix by visiting SpringVerify and updating the stage with the new stage

To learn more, reach out to cs@springverify.com