---
title: Greenhouse Duplicate Candidates: Merge and AI Review | Remqa
url: https://remqa.com/blog/greenhouse-duplicate-candidate-merge
updated: 2026-11-15
---

[Home](https://remqa.com/) / [Blog](https://remqa.com/blog) / Greenhouse Duplicate Candidates: Merge and AI Review

Recruiting AI

# Greenhouse duplicate candidates: review merges before IDs and history change

Review Greenhouse duplicate candidates, choose the primary profile, protect application history and update external AI systems after a merge.

Remqa · November 15, 2026 · 5 min read

**Short answer:** To merge duplicate candidates in Greenhouse, review the matching profiles, choose the primary candidate and confirm which conflicting values will survive. A Duplicate tag does not prove the records belong to one person, and merges cannot be undone. External AI tools also need to reconcile candidate IDs after the merge.

- Duplicate tagging and auto-merge use different matching rules
- Manual merges prioritize the primary profile when listed fields conflict
- A merge cannot be undone, so review identity and application context first
- Update external candidate references and verify scheduled interview links

By the Remqa engineering team · Last updated November 15, 2026

A recruiter merges two Greenhouse profiles. The combined profile looks right, but an external sourcing tool still points at the secondary candidate. A queued AI task then works from an identity that no longer appears in the ATS. Preventing this starts before the merge, with an explicit decision about the person, the primary profile and every system that stores their candidate reference.

Greenhouse provides native duplicate detection, manual merging and auto-merge. The AI review packet, downstream reference map and action checks below are recommended integration controls. They are not claims that Greenhouse provides a native AI merge reviewer.

## Separate a duplicate warning from a merge decision

The Duplicate tag flags a possible match under the organization's duplicate settings. Greenhouse documents email address, phone number and LinkedIn profile URL as default tag criteria. A Site Admin can optionally include name. Those signals help a recruiter find records worth checking. They do not establish that two profiles represent the same person.

Auto-merge uses separate, stricter criteria. It can match on email or phone, with additional conditions configured in organization settings. When additional criteria are selected, all selected fields must match exactly. Do not assume every tagged profile will be merged automatically. Do not let an AI tool treat a name match as permission to combine records.

> **Treat merge review as an irreversible identity decision.** Greenhouse says candidates cannot be un-merged. An AI suggestion should remain a proposal until an authorized operator has checked both profiles and the selected primary record.

## Check permission and privacy boundaries first

Site Admins can merge candidates and prospects. Job Admins need the relevant merge permission in a custom permission level. Greenhouse also requires equal job-based permissions across all jobs the candidate has applied to for a Job Admin merge. The candidate cannot be anonymized. Profiles also cannot be merged if data from either profile has been deleted through the GDPR feature.

Build permission checks into the review workflow before fetching extra evidence. If the reviewer cannot access every relevant application, route the case to an appropriate administrator. Do not copy restricted information into a shared AI summary to make the review easier. A broader summary audience does not inherit the right to see every source profile.

## Choose the primary profile by inspecting conflicts

For a manual merge, Greenhouse prioritizes the primary profile when listed fields conflict. That includes current company, current title, source, recruiter, coordinator, referral, Job Forms and the interview kit URL. The primary choice therefore changes more than the candidate name shown at the top of a page.

| Review area | Documented merge behavior | Operator check |
| --- | --- | --- |
| Conflicting single values | Primary profile values take priority for the listed fields | Confirm owner, source and referral intent |
| Multi-value information | Listed information such as emails, tags, scorecards and attachments combines | Inspect the resulting context for the right person |
| Interview kit URL | A conflict can affect scheduled interviews on the secondary profile | Manually update affected interviews |
| Secondary candidate ID | It no longer appears in the app or API after merging | Repair external references |

Start from the intended primary candidate profile and choose Merge with another candidate. The review flow also lets the operator switch candidates before confirming. For a bulk merge, select the primary profile explicitly. Avoid batch approval based only on a shared contact detail, especially when referral credit or agency ownership is involved.

## Keep person information separate from applications

Greenhouse distinguishes candidate-specific information from application-specific information. Its auto-merge documentation lists stage, source, status, recruiter, coordinator, application questions and attachments as application-specific. A person applying to different jobs is not evidence that those applications should be flattened into one hiring decision.

An AI review packet should show each job and application context separately. Ask the recruiter to confirm which hiring process is active and which historical process is only background. Do not summarize a rejection on one role as a universal rejection of the person. The same distinction matters when moving between [Greenhouse prospects and candidates](https://remqa.com/blog/greenhouse-prospects-vs-candidates).

## Understand what auto-merge leaves for manual review

Auto-merge is not retroactive. Existing duplicates still require manual handling. Greenhouse also documents exclusions, including profiles created through Harvest API or Candidate Ingestion API, confidential-job matches, agency submissions, specified referral cases, private candidates and profiles with anonymized data. Job Board API submissions have a different boundary and can be merged automatically.

That matters for recruiting AI. A custom importer cannot assume its newly created Harvest records will be cleaned up by the native auto-merge setting. Make duplicate review part of the importer design. Check the actual ingestion route and test representative cases rather than treating one account setting as universal protection.

## Prepare an AI review packet with a narrow job

1. Collect the two candidate references and the reason the pair was flagged.
2. Show matching contact details alongside conflicting identity evidence.
3. List each job, application state and ownership difference separately.
4. Propose a primary profile and explain which conflicting values would take priority.
5. Show scheduled interviews and external systems that need a follow-up check.
6. Ask an authorized operator to approve the exact pair and primary choice.

Keep uncertain cases open. Shared agency addresses, reused phone numbers or conflicting employment histories deserve human investigation. Bind the approval to the profile references and reviewed evidence. If either profile changes before execution, reload the review instead of reusing an old approval. This is a custom engineering pattern for [recruiting AI agents](https://remqa.com/ai-recruiting-agents), not a native merge guarantee.

## Reconcile external IDs before resuming queued work

Greenhouse warns that merging secondary profiles into a primary profile can cause downstream integration errors because the secondary candidate ID is no longer available in the app or API. Its candidate_merged webhook includes candidate_id and new_candidate_id fields to help external systems maintain the correct reference.

In the integration, retain an audit record connecting the retired reference to the surviving profile. Pause affected queued actions until that mapping is checked. Reload the current profile, application and permitted audience before generating a fresh summary or sending a message. Verify scheduled interviews separately when the interview kit URL conflicts.

If a merge request returns an uncertain result, inspect the ATS state before retrying. Do not issue the same identity-changing action again merely because the client timed out. Test this recovery path with the webhook and queue behavior your integration actually implements.

## How Remqa helps with Greenhouse duplicate workflows

Remqa can build the review packet, candidate reference reconciliation and queue checks around your recruiting tools. The work starts with your real permission model and hiring process, then tests both an approved merge and a case that must remain separate.

If duplicates are part of an [ATS migration](https://remqa.com/ats-migration), include the surviving candidate mapping in the migration handoff. Walk an engineer through a duplicate pair and the tools that consume it. The useful outcome is one reviewed identity with application context and external references still attached.

## Questions people ask.

**Q: Does a Greenhouse Duplicate tag automatically merge candidates?**
No. The tag identifies a possible duplicate under your organization settings. Auto-merge is a separate feature with stricter matching criteria and exclusions.

**Q: Can a Greenhouse candidate merge be undone?**
No. Greenhouse says candidates cannot be un-merged. Review the primary profile and conflicting values before confirming either a single or bulk merge.

**Q: Will auto-merge clean up existing Greenhouse duplicates?**
No. Greenhouse documents that auto-merge is not retroactive. Existing duplicate profiles still need manual review and merging.

**Q: Does Greenhouse auto-merge candidates created through Harvest?**
Greenhouse says profiles created through Harvest API or Candidate Ingestion API are not evaluated by auto-merge. Job Board API submissions have a different boundary and can be merged automatically.

**Q: What should an AI integration do after a candidate merge?**
As a custom integration design, record the old and surviving candidate references, reconcile queued work and reload current profile and application context. Confirm the correct person and job before any later write or message.

Book a free 30-minute call with an engineer: https://calendly.com/meghanaj-connect/30min