Skip to main content

Managing requesters

A requester is a record of who submitted a request to your parish — a Mass intention, an offering, a memorial, or any other workflow. Every time someone submits a request (online, by phone, or in person), a requester profile is created or matched.

Requesters are not the same thing as People or login accounts. See Understanding parish records for how these records relate to each other.

The requesters page​

Navigate to Admin Dashboard → Identity Management → Requesters. The page displays a list of all requester profiles with the following controls:

  • Search — find requesters by name, email, or phone.
  • Type filter — show all, or filter to Registered or Walk-in.
  • Sort — order by total intentions, last intention date, total paid, or name.
  • Pagination — the list shows 25 requesters per page.

Each row displays the requester's name, contact information, registration type, identity icons, intention count, total paid, last intention date, and an actions menu.

Table columns​

  • Name — shows the requester name with a small icon that indicates the requester kind:
    • single person
    • joint household / couple
    • organization
  • Contact — shows the requester's email and phone, when available.
  • Type — shows whether the requester is Registered or Walk-in.
  • Identity — shows compact icons with tooltips for linked identity records:
    • Key icon — linked login account
    • Person icon — linked Person record
    • Home icon — linked household
    • Warning icon — needs identity review

Muted icons in the Identity column mean that link does not currently exist.

Identity details​

The full text identity badges and labels appear in the View dialog, not in the table. Open a requester profile when you need to see the exact linked login account, Person record, household, or identity warnings in detail.

Requester attributes​

Every requester has two independent attributes:

Registration status​

  • Registered — linked to a login account. The parishioner can sign in and see their request history.
  • Walk-in — no login account. Created from in-person visits, phone calls, or guest checkout.

Requester kind​

  • Individual — a single person.
  • Joint household — one requester profile representing two people together (e.g., "Bud & Caroline Ederer").
  • Organization — a non-person entity such as a funeral home, school, ministry, or business.

These are independent. A requester is described by both together — for example, "Registered Individual" or "Walk-in Organization."

Viewing a requester​

Click the three-dot menu on a requester's row and select View. The detail dialog shows:

  • Contact information — name, email (with verification status), phone, address, and notes.
  • Statistics — total intentions, total paid, first and last intention dates, memorials and memorial payments (if applicable).
  • Intention history — a paginated table of all Mass intentions submitted by this requester, with status badges and links to invoices and receipts.
  • Memorial history — if applicable, a table of memorial offerings with payment status.
  • Identity links — which login account, Person record, and household are connected to this requester (read-only).

Editing a requester​

Click the three-dot menu and select Edit. You can update:

  • Requester kind — switch between Individual, Joint Household, or Organization. Each kind shows different name fields.
  • Name fields — depending on the kind: first/last name for individuals, primary and secondary names for joint household, or organization name and contact name for organizations.
  • Email and phone.
  • Preferred contact method — email or phone.
  • Address — with address autocomplete.
tip

If you just need to fix a typo in a phone number or email, edit the requester directly. You don't need to merge anything.

Merging duplicate requesters​

Duplicates happen when the same person submits requests on different occasions — once online and once in person, or after a data import creates a second profile.

Merging 2 requesters​

  1. Select both requesters using the checkboxes in the table.
  2. Click Merge Selected (2).
  3. Choose the target — pick which requester profile survives. The other merges into it.
  4. Resolve conflicts — for any field where the two records disagree (email, phone, etc.), choose which value to keep. You can also enter a custom value.
  5. Review the impact — the system shows what will move: Mass intentions, invoices, receipts, and other linked data.
  6. Confirm — type MERGE and apply.

Merging 3 or more requesters​

  1. Select all the duplicate requesters using the checkboxes.
  2. Click Merge Selected.
  3. Choose the kept requester once — all others merge into it.
  4. Resolve conflicts once — you see all conflicting values from every record and pick the best one. Values marked "Recommended" are the system's suggestion.
  5. Confirm — type MERGE and apply. The system processes the merges in sequence.

When a Person merge is required first​

If two requesters point to two different Person records, the system will block the requester merge and show a warning. You need to merge the People first in the People tab, then come back to finish the requester merge.

Merge People before Requesters

If both the People tab and the Requesters tab have duplicates for the same individual, always clean up People first. See Understanding parish records for why this matters.

Login accounts during a merge​

If two requesters are linked to different login accounts, the system asks you to choose which account stays attached to the surviving requester. The other account is not deleted or combined — it simply becomes unlinked.

The system never merges two login accounts into one.

What's next​