Requests
Track gift / aid requests end-to-end: the public form collects them, your team triages, fulfills, and marks them complete. PII is redacted at completion to keep your audit log compliant.
Who this is for: anyone with requests.manage (full) or requests.read (view-only).
What’s here
| Article | What it covers |
|---|---|
| Creating a request | Submit a request from the admin side (e.g. on behalf of a phone caller). |
| Managing requesters | The Requesters tab: contacts, consent tiers, history. |
| Snapshotting PII | Why and how recipient name gets frozen at completion. |
| Campaign link & codes | Tie requests back to the campaign that drove them. |
Public side (the form members of the public fill out) lives in end-users / Submitting a gift request.
Deleting a request
Each request row has a delete action (the ✕ at the end of the row on desktop, Delete on the mobile card). It asks for confirmation naming the requestor, then permanently removes the request — there’s no undo, and the deletion is recorded in the audit log. Use it for test entries and duplicates; for fulfilled requests, prefer marking them done so your history and reports stay accurate.
Last updated: 2026-06-11 · Applies to: CartonCrew v1.119+