Greenhouse and Ashby
Elsin verifies the candidates in your Greenhouse or Ashby and writes the verdict back as a tag and a note.
Setup takes a few minutes: see connect your ATS. This page is what happens after.
The flow
- A candidate applies in your ATS. It sends Elsin a signed webhook.
- Elsin checks the signature before reading anything, imports the candidate into an unpublished copy of the job, and scores them on passive signals.
- The first verdict is written back, usually Elsin: Low risk or Elsin: Not yet verified.
- When you move the candidate past screening, Elsin emails them once, asking for the two-minute check.
- Each later change of verdict replaces Elsin's tag and adds a note.
When the email is sent
On a stage change to an interview, onsite, panel, technical, assessment, take-home, challenge, exercise, case study, final, reference or offer stage, judged from the stage's name. Ashby's own stage types are used first. Never on application, screening, review, rejection, withdrawal or hire.
It is not sent when Verify at shortlist is off, the candidate already has a current check, a request is already open, or your monthly verifications are used up. If sending fails, the request is dropped so it does not use your allowance, and the next stage move asks again.
Tags and notes
| Tag | Note |
|---|---|
| Elsin: Not yet verified | Elsin: not yet verified. |
| Elsin: Low risk | Elsin: low risk. Nothing stood out; identity not verified yet. |
| Elsin: Checked on device | Elsin: checked on device. ID and live face matched on the candidate's own device; a person has not confirmed the ID yet. |
| Elsin: Verified | Elsin: verified. |
| Elsin: Flagged for review | Elsin: flagged for a person to review. Not a rejection. |
Choose Tag, Note, Both or Off under Write verdicts back. Both is the default. Elsin only ever removes its own previous verdict tag; your own tags are never touched.
What your ATS never receives
Reasons, scores, signals, ID images, documents or anything about other employers. Only the tag and the sentence above.
Retries and errors
- The write-back queue runs every 5 minutes and tries each verdict up to 5 times. Only the newest verdict per candidate is sent.
- Each attempt is listed under Recent events in Settings, Integrations.
- If your ATS refuses the key, owners and admins get one email asking them to reconnect.
- If your plan no longer includes write-back, verdicts are held, not lost, and sent when it does again.
- A repeated webhook delivery is recognised for 35 days and ignored.
Pausing and disconnecting
Turn off Receiving candidates to pause. Nothing is imported or written back while paused. Disconnect asks whether to keep the imported candidates or delete everything imported from that ATS, including files, identity hashes and the mirrored jobs. Webhooks Elsin added itself are removed. Keys are stored encrypted and never shown again.
Jobs mirrored from your ATS do not count toward your plan's open jobs.