Review sponsor updates as a separate approver
Open Charity → Update approvals with care.sponsorship.update.approve and the sponsorship capability context. The queue lists pending updates oldest first. Approval rights are separate from drafting/management rights.
Review checklist
| Check | What to look for |
|---|---|
| Submitter | You must be a different user from the person who submitted this update |
| Target | Correct alias/facility/programme; no real beneficiary identity inferred |
| Title and body | Appropriate, accurate, non-identifying content for the approved purpose |
| Photo reference | Approved reference; no confidential filename or unsupported file transfer |
| Beneficiary eligibility | Still sponsorable at approval |
| Public-photo consent | Current PHOTO_USE_PUBLIC consent when a beneficiary update includes a photo reference |
The server applies the distinct-user rule to the submitter, not merely the original draft author. Holding both drafting and approval permissions does not permit self-approval. The same distinct-user check also applies to rejecting one's own submission.
Approve
- Open the queue and identify the target and submitted-by information.
- Read the complete message and any photo reference/consent indicator.
- Confirm it meets the approved privacy and content requirements.
- Choose Approve once.
- Verify the success message and removal from the pending queue.
- The officer can then inspect the approved record and mark it published separately.
Reject
Choose Reject, enter a meaningful reason in the displayed prompt and confirm it. A blank/cancelled reason does not complete rejection. Explain the required correction without copying unnecessary confidential facts into the reason.
Example: Omar submits an update with a photo reference. Leena sees no current public-photo consent. She rejects with “Remove the photo reference or obtain the required approved consent before resubmission.” She does not approve simply because profile-sharing consent exists; the two consent purposes differ.
Recovery and enforcement limits
If another user already decided or edited the update, the version/status check refuses the stale action and the page reloads. Re-read the current queue. An ineligible beneficiary blocks approval; arranging a transfer does not automatically make the old beneficiary update suitable to publish.
Human review remains necessary: the application cannot prove the narrative is accurate or remove personal details typed into free text. The photo consent rule described here is checked for beneficiary targets; do not treat the displayed facility/programme consent indicator as a complete media-rights approval process for every person in a photograph.