Review and merge from a record page

Purpose

Staff can investigate duplicate suggestions without leaving the record they are reading.

How It Works

A record page requests its open medium-or-stronger suggestions when the reader has duplicate-read permission. The indicator distinguishes likely matches from medium-confidence possibilities. Weak suggestions do not produce a page alert. The response can include the whole connected group, including records reached through another candidate. An authorized merger selects records and starts a plan. The current record joins the participants without automatically becoming the survivor. A Merge action also allows manual selection when detection found nothing. Reviewers can dismiss suggestions from the indicator. A request under a merged-away identity reports the survivor rather than returning an empty candidate list. The same interaction applies to contacts and organizations.

Relationships

Queue review and record-page review share candidates and dismissals. Merge planning owns the choice of participants and survivor once the page launches a plan.

Show evidence (sources, provenance, origins, pinned commits)

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Outcomes: Record-page review reveals suggestions in the current work context.Manual or detected counterparts can join a plan with the current record.
Surfaces: consoleapi
Intent sources: services-crm:docs/merging/experience/functional-requirements.md#IND-1 to IND-7, MAN-1, MAN-2 (package approved by Andrew 2026-10-13)services-crm:docs/milestones/CRM-M1-contacts-and-organizations.md#D-03

Controls

17 controls apply, from the corpus control catalogue.

TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-AZ-006 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-LOG-004 TC-LOG-005 TC-PI-001 TC-PRV-001 TC-PRV-002 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-TEN-004

Permissions

Key	Checked at	Scope
`crm.duplicates.read`	api	record
`crm.contacts.merge`	console	tenant
`crm.organizations.merge`	console	tenant

Business Rules

8 rules, 6 to be proved before approval. A rule's product intent is derived from its origin: 8 confirmed by a product decision, the rest inheriting this capability's confirmed.

Id	Rule	Kind	Enforced at	Provenance
`01`must prove Confirmed	Per-record candidate reads include every status unless filtered, return at most 100 without pagination and return no group for an empty candidate list. no proof recorded yet	policy	api	test services-crm:modules/duplicates/tests/e2e/duplicates.e2e.spec.js#answers nothing for a record in no pair at all
`02`must prove Confirmed	The response includes the connected group's records, including those related only through another candidate, for whole-group merge launch. origin: services-crm:docs/merging/experience/functional-requirements.md#IND-5 no proof recorded yet	calculation	service	test services-crm:modules/duplicates/tests/integration/services/candidates/duplicate-candidate-view.integration.spec.js#answers the four records of that group, which is the banner a record page shows
`03`must prove Confirmed	Reading candidates under an absorbed identity returns a merged-record response naming its survivor instead of an empty list. origin: services-crm:docs/milestones/CRM-M4-duplicates-and-merge.md#D-20 no proof recorded yet	policy	api	test services-crm:modules/merges/tests/e2e/merged-records.e2e.spec.js#answers 410 to the old id’s duplicate candidates, rather than an empty list
`04`must prove Confirmed	The page indicator includes open medium, high and very-high candidates, distinguishes likely high-or-above matches from medium possibilities and shows no alert for low-only or empty results. origin: services-crm:docs/merging/experience/functional-requirements.md#IND-2 no proof recorded yet	policy	console	observed react-console:components/duplicates/indicator/use-record-duplicates.ts:useRecordDuplicates
`05`must prove Confirmed	Duplicate information on a record page is visible only with duplicate-read authority. origin: services-crm:docs/merging/experience/functional-requirements.md#IND-7 no proof recorded yet	permission	console, api	test react-console:acceptance/crm/playwright/journeys/merging/CRM-ACC-0239.spec.ts#CRM-ACC-0239
`06`must prove Confirmed	Merge-authorized staff launch a plan from selected indicator records, including the current record without choosing it as survivor. origin: services-crm:docs/merging/experience/functional-requirements.md#MAN-2 no proof recorded yet	policy	console	test react-console:acceptance/crm/playwright/journeys/merging/CRM-ACC-0286.spec.ts#CRM-ACC-0286
`07` Confirmed	Merge-authorized staff receive a Merge action and additional-record picker on contact and organization pages even without detected candidates. origin: services-crm:docs/milestones/CRM-M1-contacts-and-organizations.md#D-03	policy	console	test react-console:acceptance/crm/playwright/journeys/merging/CRM-ACC-0286.spec.ts#CRM-ACC-0286
`08` Confirmed	Reviewers can dismiss an indicator candidate and see the changed decision reflected wherever that pair is displayed. origin: services-crm:docs/merging/experience/functional-requirements.md#DIS-1	policy	console	observed react-console:components/duplicates/indicator/use-record-duplicates.ts:useRecordDuplicates

Scenarios

Id	Given	When	Then	Provenance
`01`	A contact belongs to a three-record connection, including one indirect match.	An administrator launches Merge With Selected from its page.	All three join the plan and the current record is not forced to survive.	test react-console:acceptance/crm/playwright/journeys/merging/CRM-ACC-0286.spec.ts#CRM-ACC-0286
`02`	An organization has a candidate based on its name and domain.	A reviewer dismisses the suggestion on its page.	The alert clears and the pair appears among dismissed work.	test react-console:acceptance/crm/playwright/journeys/merging/CRM-ACC-0238.spec.ts#CRM-ACC-0238

Planning

Review and merge from a record page ​

Purpose ​

How It Works ​

Relationships ​