TraqCheck
Background Screening & Verification

TRACE and Greenhouse: Background Check Integration for UK HR Teams

EREleonora Rocca
12 November 2026

Jurisdiction: UK, including UK GDPR for candidate data. Statutory checks follow the rules of each UK nation.

This article is for informational purposes only and does not constitute legal advice. Employment law and screening regulations vary by jurisdiction. Consult a qualified legal professional before making compliance decisions.

A recruiter moves a candidate into the background check stage in Greenhouse. Moments later, the candidate has a consent request on their phone, the checks are underway, and the hiring team can follow progress without leaving the candidate's profile. That is the experience UK HR teams look for when they connect screening to Greenhouse.

TRACE, TraqCheck's verification agent, lists Greenhouse among its native integrations. Here is how a check starts from a Greenhouse record, how consent fits in, where results land, and how sourcing and screening can share one Greenhouse pipeline.

Why UK HR teams want background checks inside Greenhouse

Greenhouse is where interview plans, scorecards, and offers already live. Running screening from the same record keeps the hiring story in one place, from the first interview to the final check.

Three practical reasons

Recruiters stop copying candidate details into a separate screening portal

Hiring managers see where each candidate stands without chasing recruiters for updates by email

Compliance teams get one record showing who requested each check and when

UK teams also benefit from tighter data handling. Fewer exported spreadsheets and email attachments mean less personal data spread across inboxes, which fits the UK GDPR principle of keeping only what each step needs.

How TRACE integrates with Greenhouse

Greenhouse supports background check partners through its integration framework, typically using a Harvest API key and webhooks configured during setup. Greenhouse's own support articles show partners linking a trigger in the hiring plan to an order in the screening platform.

What TRACE adds once a check starts

On receiving the order, TRACE:

Requests the candidate's consent and documents it through a guided mobile portal

Searches the relevant sources for all checks in the package in parallel

Routes each result to a human verification specialist for review

Produces a plain-language report with flags, verified facts, and an audit trail

For standard digital verifications, TraqCheck states that the full flow typically completes in hours.

A note on integration details

The TRACE product page names Greenhouse, Lever, and Workday as native integrations. Configuration specifics, such as which trigger is used and which fields return, are agreed during setup, so confirm them with TraqCheck before rollout.

Triggering a check from a Greenhouse candidate record

Greenhouse integrations can start a background check at different points in the hiring plan. Choosing the right one is the first design decision.

The main options, and what each one means for your team:

Trigger pointHow it typically works in GreenhouseWhat to decide
Dedicated background check stageMoving the candidate into a named stage sends the orderWhere the stage sits in each interview plan
Offer stageCreating or approving the offer starts the checkWhether checks wait for an accepted offer
Marked as hiredThe hire event triggers the orderWhether pre-start timing allows the checks to finish

For most UK roles, a dedicated stage after a conditional offer works well. Criminal record checks usually follow a conditional offer, and a named stage gives recruiters a clear, deliberate action.

Packages by role

Each Greenhouse job can map to a TRACE package. A graduate scheme might use identity, education, and employment checks, while a finance role adds credit history where justified. Setting packages per job keeps checks consistent and proportionate. Recording the reason for each package alongside the job also helps when someone later asks why a particular check was run.

Candidate consent within the Greenhouse workflow

Consent is the first thing the candidate sees once the stage moves. TRACE sends a branded request explaining what will be checked, and the candidate completes it in minutes.

Keeping consent clear for UK candidates

Explain each check in plain language before the candidate agrees

Link to your privacy notice from the consent screen

Collect only the documents the package needs

Give a named contact for questions about the process

Clear information at this stage supports UK GDPR transparency. Candidates who understand the process also tend to submit complete information first time, which reduces back-and-forth for everyone.

Statutory checks alongside TRACE

The DBS certificate itself comes from DBS via a registered body, and any digital Right to Work check needs a provider on the official register for that purpose. Many teams add those steps to the same Greenhouse stage so recruiters see everything together, while each check runs through its required channel.

How verification results appear back in Greenhouse

Greenhouse partner integrations commonly return status and results to the candidate profile. Depending on the partner and settings, updates appear in the activity feed, on the private tab, in custom fields on the details tab, or as an attached report. Agree the placement during setup and tell recruiters exactly where to look, because a one-page internal guide with a single screenshot answers most questions before they are asked.

Access and permissions

Greenhouse's private tab and user permissions help limit who sees screening detail. Many UK teams give hiring managers a status view while a smaller HR group reviews full reports. TraqCheck's ​UK GDPR guidance for screening data covers access, retention, and lawful basis in detail.

Acting on results

A human specialist has already reviewed each TRACE result, so the report arrives ready for a decision. Any flag comes with the information behind it, and the hiring decision itself always stays with your team. Where a result needs discussion with the candidate, the recruiter can arrange that conversation from the same profile, keeping notes alongside the report.

From NINA shortlist to TRACE check in one Greenhouse pipeline

Greenhouse can also be the meeting point for sourcing and screening. NINA, TraqCheck's ​AI sourcing agent, lists Greenhouse and Lever among its ATS integrations on paid plans, syncing shortlists and candidate status.

How the two agents connect

NINA sources and engages candidates for a role, then syncs interested shortlisted candidates to Greenhouse.

The team interviews and moves the chosen candidate through the Greenhouse plan.

At the background check stage, TRACE runs the verification package.

The result returns to the same Greenhouse record that NINA's shortlist started.

For ​talent acquisition teams, that creates one continuous candidate record, running from the first message NINA sends to the final verified hire. Our comparison of ​AI hiring agents and recruitment software explains how agents and an ATS share the work.

Setting up the Greenhouse connection

Setup is mostly a series of small decisions. Making them before the technical work begins keeps the project short.

Before you start

A Greenhouse user with permission to create API credentials and webhooks

The trigger point, and which interview plans will include it

A package for each job or job family

The permission model for screening results

One or two test candidates, usually internal volunteers

Rolling out in stages

Start with one department or office, ideally one with steady hiring volume. Run real hires through the stage for a couple of weeks, then review what recruiters and candidates found confusing. Small adjustments at that point, such as renaming a stage or clarifying the consent wording, are easy to make before the wider rollout. Once the pilot runs cleanly, extend the stage to the remaining interview plans in one change.

A single pipeline for every hire

Greenhouse already organises how a team interviews and decides. Connecting TRACE adds verification to that structure, with consent on the candidate's phone, parallel checks, specialist review, and results on the same profile. Add NINA at the top of the funnel, and the whole journey runs through one pipeline. The ​verification agent slots into a stage you already run. The next step is a setup plan for your own Greenhouse instance, so ​start verifying and map stages, packages, and permissions together.

Frequently asked questions

Does TraqCheck integrate with BambooHR or Greenhouse for UK HR teams?

Greenhouse is a native TRACE integration, alongside Lever and Workday. BambooHR is not listed among TRACE's native integrations, so teams using it would connect through the TRACE API.

How do you run a background check from Greenhouse?

Most teams move the candidate into a configured background check stage, which sends the order to the screening platform. Some integrations trigger at the offer or hire stage instead.

Where do background check results show in Greenhouse?

Results typically appear on the candidate profile, in the activity feed, private tab, details tab fields, or as an attached report. The exact placement depends on configuration.

Can NINA and TRACE both work with Greenhouse?

Both do. NINA lists Greenhouse among its ATS integrations on paid plans, syncing shortlists, and TRACE lists Greenhouse as a native integration for verification.

Who can see background check results in Greenhouse?

Access depends on Greenhouse permissions and private tab settings. Many UK teams limit full reports to a small HR group and give hiring managers status only.

Does the Greenhouse integration cover DBS checks?

DBS certificates are issued by DBS through registered bodies. Teams often track that step in the same Greenhouse stage, while TRACE runs identity, employment, education, and international checks.

The Human Operating System for Hiring

Get in touch