Skip to main content

Identity review queue

The Identity Review Queue is where Sacramentum surfaces identity matches it isn't fully sure about. When a parishioner submits a Mass intention, fills out a sacrament workflow, or registers their family, the system tries to figure out whether they already have a Person record. Most of the time it can decide automatically, but when the signal is weak — a name match without an email, two close candidates, an unusual joint-requester case — it queues the match for an administrator to review instead of guessing.

This article explains how items reach the queue, how to read them, and how to resolve each kind of task.

The identity review page​

Navigate to Admin Dashboard → People & Places → Identity Review. The page opens with three task summary cards across the top, then a search bar and filters, then the queue itself.

Task summary cards​

  • Pending — every queue item that still needs a decision.
  • Actionable — pending items where you can resolve directly from the queue, typically by linking the source record to one of the candidates.
  • Manual review — pending items that need a closer look outside the queue (for example, weak name-only matches that may need the full Person profile to compare).

Search and filters​

  • Search — match by source name, email, or phone.
  • Status filter — Pending (default), Resolved, Dismissed, or All.
  • Queue type filter — narrow to a particular flow such as Sacrament identity bridge, Family profile bridge, Household cluster, or Manual review.

Queue cards​

Each pending item appears as a card with:

  • An icon indicating the source type — baptism candidate, wedding party member, funeral celebration, quinceañera honoree, requester, household cluster, or generic.
  • A task title — for example, Link requester to Person, Link Person to Household, Set household primary contact, Joint co-requester review.
  • A confidence badge — High (green), Medium (sky), or Low (amber).
  • A short reason explaining why the system queued the item — name-only match, joint-name detected, potential duplicate, and so on.
  • The source name and any contact details Sacramentum has for the originating record.

Click a card to open the Review dialog, which shows everything you need to decide.

How items reach the queue​

When any write path creates a Mass intention, sacrament case, family profile, or other identity-bearing record, Sacramentum runs identity resolution. The resolver looks at the requester's user account, email, phone, and name and walks through a priority chain to find the right Person.

When the chain produces a single confident match, the system links automatically and you never see a queue item. When the chain finds:

  • multiple candidates that look similar,
  • a name-only match with no email or phone to corroborate,
  • a joint requester ("Bud & Caroline") whose secondary name might match more than one Person, or
  • a household-level pattern where several People should probably share a household,

the system creates an Identity Review Queue entry and waits for human judgment.

Each entry records the source collection, the workflow type, the candidate People or Households the resolver considered, and the signals that triggered the queueing — exact name match, same first initial plus same last name, matching email, matching phone digits, and similar.

Reviewing an item​

Click any pending card to open the review dialog. The layout has three sections.

Source panel​

The left side describes the source record — the document that triggered the review. For a Mass intention requester this is the requester's name, contact info, and the workflow ("Requester to Person link"). For a sacrament case this is the candidate's name, the sacrament involved, and the celebration date or location. For a household cluster it's the cluster of People that may share a home.

A colored banner above the source panel summarizes the situation — Strong signal, Name-only caution, Joint co-requester, Household primary contact, or Generic — so you know at a glance what kind of decision you're being asked to make.

Candidate list​

The right side lists the candidate People or candidate Households the resolver thinks might match. Each candidate shows their name, status, household, contact info, and a list of matching signals — Exact name, Same first name, Same last name, Matching email, Matching phone — so you can see why the resolver flagged each one.

Pick the candidate that matches the source record by clicking it.

The footer contains the action buttons. The exact set depends on the workflow type, but you will see one or more of:

  • Link selected and resolve — link the source record to the candidate you picked. The button label varies by workflow (for example, Link selected Person and resolve, Set primary contact and resolve, Link selected Household and resolve) but the effect is the same: the link is created and the queue item is marked Resolved.
  • Create new Person — when no candidate is the right person, create a fresh Person from the source record's data and link to it. Available only on workflows that support creating identities (requester-to-Person and joint co-requester reviews).
  • Dismiss — close the queue item without linking. Use this when none of the candidates are a real match and creating a new Person isn't the right move either. The item moves to Dismissed.
  • Cancel — close the dialog without resolving.

Two lists and three answers​

The queue is split in two so the page shows only what needs you.

  • Needs a decision (the list that opens first, and the one the sidebar badge counts) — payment problems, login accounts, a name that no longer matches its linked person, sacrament participants, and records with a broken link.
  • When you have time — possible duplicates: a new record that shares an email or phone with an existing one, a couple whose second person is not linked yet, and two people of a couple who are in different households. Nothing is broken and nothing is waiting on these, so work through them when it suits you. Data Cleanup opens this list from its Optional reviews card.

When an item asks whether two records are the same person, you have three answers:

  • Yes, same person — link or merge, as the item offers.
  • No, different — record that they are different people.
  • Not enough information — leave the records separate without saying they are different. Use it when you cannot tell. It is not remembered as proof that they differ.

Not sure, skip only moves you to the next item and records nothing.

Individual and couple profiles​

A person can have a profile for their own requests and another for requests made with a spouse ("John Smith" and "John and Jane Smith"). They are two profiles of the same people, not duplicates, and they are never merged into one. Asking as a couple one day and alone the next never changes the other profile or the requests already on it. If the queue compares the two, the answer Yes, same person. Keep both profiles. only joins the two people when the names show they are the same; both profiles stay as they were.

Confidence levels​

The confidence badge on each card reflects how strong the resolver's signal is.

ConfidenceMeaning
High (green)The resolver found a strong signal — usually exact email or phone match plus name corroboration. Almost always safe to approve.
Medium (sky)The resolver found a partial signal — a name match plus one secondary clue. Usually correct but worth a glance.
Low (amber)The resolver found only a weak signal — name-only or ambiguous. Inspect carefully; these are the most likely to be wrong.

Confidence is a hint, not a verdict. Even High items are queued because the resolver wanted a human to confirm, so always look at the candidate list before approving.

Advanced tools​

Administrators see an Advanced tools button on the page header. It opens a side sheet with manual identity operations that don't belong inside a single queue item:

  • Manual link / unlink between requesters and People, People and Households, or Households and their primary contact.
  • Manual resolve of an item when the in-dialog flow doesn't fit your scenario.

These are escape hatches for unusual situations. Most day-to-day work happens inside the queue dialog itself.

What happens after a decision​

When you approve a link, Sacramentum updates the source record to point to the chosen Person or Household and marks the queue item Resolved with an audit log entry. If the link affects a Person or Household that has downstream records — Mass intentions, invoices, receipts, sacrament cases — the identity merge service cascades the update so every related record stays in sync.

When you dismiss an item, the source record is left unchanged and the queue item moves to Dismissed. Dismissed items remain searchable so you can see what was reviewed and decided.

You can switch the Status filter to Resolved or Dismissed to review past decisions and confirm the queue history is what you expect.

What's next​