Polyguard PreScreen for Lever¶

Download this guide as a PDF

1. Overview¶

PreScreen protects each job application with a Polyguard Trust Check: a short check the candidate completes on their phone. Unverified candidates are held in the default new applicant stage, and verified ones are advanced automatically. The verification details are recorded as a note on the opportunity.

How it works¶

Applications reach Lever by two paths:

The job board is a wrapper around your Lever configuration, rendering your live Lever postings with their full application forms.

What you will configure¶

• A PreScreen app in the Polyguard Console, with its own hostname
• One Lever API key with a fixed set of permissions
• A Human Verification stage in your pipeline
• An Application created webhook from Lever to Polyguard

Who does what¶

Steps marked (Polyguard) will be performed by a Polyguard staff member. Lever steps need a Lever Super Admin: only Super Admins can generate API credentials and configure webhooks.

2. Prerequisites¶

3. Collect your Lever values¶

Find these values under Settings in Lever. Keep the values to hand; you will paste them into the Console in Section 4.

3a. Lever API key¶

The key should be configured with the following endpoint permissions. Allow access to confidential data can be left off.

1. Open Settings → Integrations and API → API Credentials.
2. Under Lever API credentials (not the Postings API key at the top of the page), click Generate New Key.
3. Name the key Polyguard PreScreen. The name and an optional logo appear on the notes and stage changes Polyguard writes.
4. Under Permissions, tick the endpoints in the table above.
5. Click Generate key, then Copy Key. This is the only time Lever shows it.

3b. Site slug¶

The {site} in your Lever-hosted job site URL, https://jobs.lever.co/{site}. For your account this is <your-lever-site>.

3c. The Human Verification stage¶

Lever pipeline stages are shared across all postings. Teams whose applicants land in, or should advance into, a different stage can be listed under Pipeline stages by team on the Candidate verification card of the PreScreen settings page.

1. Open Settings → Pipeline and archive reasons.
2. Add a stage named Human Verification directly after the stage new applicants land in (by default New applicant).

Candidates who pass a Trust Check are moved into it; unverified candidates stay in the landing stage.

3d. Perform-as user (optional)¶

Stage moves and notes are attributed to the API key by default. To attribute them to a Lever user instead (for example a shared recruiting-ops account), open that user in Lever and copy the id from the URL.

3e. Archive reason (optional)¶

When an emailed Trust Check is not completed within 7 days, Polyguard revokes the link. If you also want the candidate archived, pick an archive reason under Settings → Pipeline and archive reasons and note its id. Leave this out to keep unverified candidates held in the landing stage.

4. Configure the app in Polyguard¶

4a. Create the PreScreen app (Polyguard)¶

Console → Create App → app type PreScreen.

Creating it reserves a hostname of the form {account-slug}.prescreen.polyguard.ai.

4b. Check the hostname (Polyguard to change)¶

Settings → Prescreen → Hostnames shows the host this tenant is served on. Account admins can read it; only Polyguard staff can change it.

The webhook URL in Section 5 is built from it, and so is the address Polyguard delivers verification results to.

4c. ATS connection¶

Settings → Prescreen → ATS connection, provider Lever.

Click Save ATS configuration. Secrets clear from the form on save and show their last 4 characters afterwards; leaving a secret blank keeps the stored value rather than clearing it.

4d. Branding¶

Settings → Prescreen → Branding: company name, colors, logo, favicon and theme stylesheet, plus the careers title and intro shown above the roles list. Optional extras on the same card: your site navigation and header button, the roles list layout (department tabs) with a notice and call to action. Changes reach the careers site within a minute.

5. Register the webhook in Lever¶

Lever notifies Polyguard whenever an application is created.

5a. The webhook URL¶

https://<your-polyguard-domain>/api/ats/webhook. The Console shows it in the ATS connection form above Webhook signing token once a hostname is saved; use it verbatim.

5b. Create the webhook¶

1. In Lever, open Settings → Integrations and API → Webhooks.
2. Toggle Application created on and click Add webhook.
3. Enter the URL from 5a.
4. Copy the Signature token Lever shows for this webhook.
5. Click Verify connection. Lever sends a sample event and reports success. If it fails because the Polyguard site is not yet live at the hostname, Lever still delivers real events once it is.

5c. Save the signing token in the Console¶

Back in Settings → Prescreen → ATS connection, paste the token into Webhook signing token and click Save ATS configuration.

6. Support¶

• Email: [email protected]
• Console: console.polyguard.ai
• Sending Trust Check emails from your own domain: Sending From Your Domain

Lever documentation¶

• Lever API reference
• Generating and using API credentials
• Webhooks: set up, signing and delivery history

For Lever platform issues unrelated to Polyguard, contact your Lever administrator or Lever Support.