Skip to Content
ModulesRequestsManaging requesters

Managing requesters

Requesters are the people / orgs who file requests with you. The Requesters tab is a full directory — each record keeps contact details, consent, a status, a Verified marker, request history, and an optional note.

Who this is for: Editor / Admin / Owner with requests.manage.

Steps

  1. Requests → Requesters tab.
  2. Search, or filter by Status (Active / Inactive) and Verified only. Click a row to open its detail page.
  3. The detail page shows:
    • Status badge — Active or Inactive. Use Deactivate / Reactivate to flip it.
    • Verified badge — a trust marker an admin sets once they’ve confirmed the requester’s identity. Use Verify / Unverify; the date and who verified are recorded.
    • Contact info (name, email, phone, organisation).
    • Consent — Campaign contact and Marketing & newsletters, each captured with how/when it was given. See admin → Consent tiers.
    • Request history — every request they’ve filed, with recipient, date, items, and status (Open / Completed, plus a “picked” marker).
    • Notes — internal-only free-text scratch.
  4. Click Edit to change fields (including Status and Verified) and Save.

Verified & trust

Marking a requester Verified is a deliberate trust signal: an admin has confirmed who they are. A verified — or otherwise well-known — requester lowers the fraud risk on the requests they file, so verifying your regulars makes triage faster and safer.

Bulk operations

From the Requesters list:

  • Tick multiple rows.
  • Bulk actions bar appears.
  • Set consent tier in bulk (e.g. upgrade a cohort to Marketing after they opted in via a campaign).
  • Export the selection as CSV.

What you’ll see

Video — coming soonManage requesters + consent tiersRecorder brief: V15 — Open a requester, bump consent None → Campaign, then bulk-select 3 and upgrade to Marketing.

Common issues

  • Requester appears twice — the public form created a new record because the email was a typo. Merge: open the duplicate, copy the history into the canonical one, then delete.
  • Consent tier won’t drop below current — by design; downgrades require an explicit confirmation modal (audit-logged).
  • Request history empty — the Requester has no linked requests yet.
  • Requester missing from the list — check the Status filter; deactivated requesters are hidden when you filter to Active only.

Last updated: 2026-06-09 · Applies to: CartonCrew v1.110+

Item categoriesSnapshotting PII