Skip to content

Process 10 — Moderation decision (admin)

Process 10 — Moderation decision (admin)

Section titled “Process 10 — Moderation decision (admin)”

Parent spec: 10-admin-console · Consumes: 03-ad-moderation §6–§7.

Cloudflare Access authenticates an administrator viewing the moderation queue. The administrator claims a creative and approves or rejects it. The API records the decision and audit entry, resolves conflicting updates and emails rejection notices.Cloudflare Access authenticates an administrator viewing the moderation queue. The administrator claims a creative and approves or rejects it. The API records the decision and audit entry, resolves conflicting updates and emails rejection notices.

Notes

  • The CF Access JWT is verified at the edge; the Cf-Access-Authenticated-User-Email and Cf-Access-Jwt-Assertion headers are injected before any worker code runs.
  • Optimistic locking is not a new primitive — it reuses 03 §E9 (WHERE state='pending'). The admin UI sends no If-Match; conflicts surface as ad.state-conflict.
  • The moderation_claims soft lock prevents two admins reviewing the same ad. Implicit release on decision; explicit DELETE on navigate-away.
  • Audit row stores sub (stable) and email (display). Email may change; sub does not.
  • bump_strike=true issues a strike via 02 — only used on revoke for policy/copyright; not on initial reject.