Applicant tracking

Connecting an ATS

Connect your applicant tracking system and Reckn works from the jobs and candidates already in it — no parallel upload process, no second system of record. Greenhouse is supported today. Reckn works standalone with manual uploads if no ATS is connected.

What the connection does

Once connected, Reckn can:

  • List the jobs in your ATS and import the ones you choose
  • Read the job post behind each imported job, and use it as the source document criteria are extracted from
  • Pick up candidates as they reach a stage you nominate, and pull their resume
  • Evaluate the resume against that job's locked criteria set
  • Write the result back against the candidate in the ATS

Nothing is evaluated automatically until you turn that on. The connection by itself imports and listens; what happens next is controlled by the automation settings.

Before you connect

Required

The Greenhouse user who authorizes the connection must hold Site Admin. A non-admin authorization produces a connection that is denied on nearly every call — it will appear to connect and then fail on use.

Strongly recommended

Authorize with a service account rather than an individual. A connection tied to a departing employee dies with their account, and every evaluation stops with it.

Connecting Greenhouse

  1. Open ATS settings

    In Reckn, go to Settings and open the ATS connection tab.

  2. Start the Greenhouse connection

    Choose Greenhouse. Reckn hands off to Greenhouse's authorization screen. Sign in as the Site Admin service account if you are not already.

  3. Approve the access request

    Greenhouse shows the permissions Reckn is asking for. Approve, and Greenhouse returns you to Reckn.

  4. Confirm the connection is live

    The ATS connection tab now lists Greenhouse. Reckn provisions the pieces it needs on its own from here.

Video docs/ats/01-connect-greenhouse.mp4

The full connection handoff, from ATS settings through Greenhouse authorization and back.

What Reckn sets up

Immediately after authorization, Reckn provisions two things in Greenhouse so it never has to ask you to configure them by hand:

  • A candidate tag used to mark candidates Reckn has evaluated, so evaluated and un-evaluated candidates are distinguishable inside Greenhouse itself.
  • Webhook subscriptions so Greenhouse tells Reckn when something relevant happens, rather than Reckn polling for it.
Subscription Why Reckn needs it
candidate_stage_change The arrival signal. When a candidate reaches your trigger stage, this is what tells Reckn to evaluate them.
job_post_created A new posting appeared and may need a scorecard.
job_post_updated The requirements changed. Criteria extracted from the old text may no longer match what you are hiring for.
job_post_deleted The posting is gone; nothing further should be evaluated against it.

Access Reckn requests

Reckn asks Greenhouse for the narrowest set of Harvest permissions that supports the loop above — read access to the hiring data it evaluates, and write access limited to the note and tag it puts back.

Area Access Used for
Jobs and job posts Read Listing jobs to import, and reading the post as the source document
Candidates and applications Read Identifying who arrived and which job they applied to
Attachments Read Pulling the resume to evaluate
Interview stages Read Letting you pick a trigger stage from the real stage list
Notes Create Writing the evaluation result back against the candidate
Candidate tags Read and write Marking a candidate as evaluated
Webhooks Full Creating and maintaining its own subscriptions, and removing them on disconnect
Note

Reckn does not move candidates between stages, reject candidates, or change any hiring decision in your ATS. It writes an evaluation and a tag. The decision stays with your team.

Connection settings

Trigger stage

The stage that means "evaluate this candidate." When a candidate moves into it, Reckn treats that as the arrival signal. Reckn reads the stage list from your ATS so you choose a real stage rather than typing a name.

Result visibility

How visible the evaluation is to people inside Greenhouse once it is written back.

Setting Who sees the result in Greenhouse
admin_only Restricted to admins
private Limited visibility
public Visible to everyone on the job

Automation

Each of these is off until you turn it on, and each one hands a decision from a person to the system. They chain — auto-weight needs auto-generate, auto-lock needs auto-weight.

Setting What it does
Auto-generate criteria on job arrival When a new job arrives, extract criteria from the job post and prepare the scorecard.
Auto-weight criteria After generation, weight the criteria by pairwise comparison. Criteria stay unlocked for review.
Auto-lock scorecard Lock criteria after weighting without manual review. Can still be unlocked later.
Auto-evaluate on candidate arrival When a candidate arrives for a role with locked criteria, run the evaluation immediately.
Re-generate criteria on job post change When the posting text changes, rebuild the criteria from the new version.
Before enabling auto-lock

Auto-lock skips human review of criteria and weights. Everything is still recorded and still explainable — but the person who would have caught a badly worded criterion never saw it. Run with review on for a few jobs first.

Screenshot docs/ats/02-connection-settings.png

ATS settings — trigger stage, result visibility, and the automation toggles.

What gets written back

When an evaluation completes, Reckn writes two things into Greenhouse:

  • A note on the application carrying the evaluation result, at the visibility you configured.
  • The evaluated tag on the candidate, so anyone working the pipeline in Greenhouse can see at a glance what has been through Reckn.

The full record — per-criterion assessments, reasoning, confidence, weights, artifact — stays in Reckn. The note is the summary that belongs where recruiters already work.

Events and delivery

Every inbound ATS event is recorded, so you can see what arrived and what Reckn did with it. Two cases are worth knowing:

  • Failed delivery. If writing a result back to the ATS failed, delivery can be retried for that run without re-running the evaluation.
  • Unassigned events. Candidates can arrive for jobs you never imported into Reckn. Those events are held rather than silently dropped, and can be dismissed once you have decided the job is out of scope.
Screenshot docs/ats/03-ats-events.png

The ATS events view, with a failed delivery being retried.

Disconnecting

Disconnecting removes the connection and the access it held. Everything Reckn already evaluated — runs, criteria, reports, artifacts, audit trail — stays in Reckn. Reconnecting later means authorizing again and re-importing the jobs you want.

Other ATS platforms

Greenhouse is the first provider, not a special case. ATS support sits behind a provider registry: each platform contributes an adapter, and the rest of Reckn only ever sees normalized shapes — a job, a job post, a candidate, an application, a resume attachment, and a result to deliver.

Adding a platform means implementing that adapter for it:

Adapter responsibility What it covers
Authorization The platform's OAuth flow and credential storage
Ingestion Listing jobs and posts, and normalizing them
Arrival signal Webhook subscriptions, or polling where webhooks do not exist
Resume retrieval Fetching the attachment to evaluate
Result delivery Writing the result back in whatever form the platform supports

Provider-specific behaviour stays inside the adapter. The evaluation core — criteria, weighting, locking, scoring, artifacts — is identical whichever ATS the work arrived from, which is why a result is comparable across sources.

Note

If you need a platform other than Greenhouse, tell us which one — adapter work is prioritized by what customers actually run on.