Your account
HOL-D026Story implementation: In progress

Review member posts before they appear

operations · Proposed launch phase 2

Start from Home

Review as Group moderator

User story

As a group moderator, I want to review and resolve pending contributions so I can keep group participation useful and safe.

Draft requirements for review · Updated 2026-10-19

What the app should do

  • Review only contributions and reports for the moderator’s assigned group.
  • Approve a sample submission or reject it with a reason; keep reporter identity withheld and escalate matters outside assigned scope.
  • Remaining acceptance: connect decisions to member submission/publication state and enforce group scope; sample queue buttons do not prove production permissions.
  • Hide or restore previously published content only within the assigned group, with a recorded reason and reviewable prior state; do not permanently destroy reports/evidence.
  • Review an assigned-group participation case and record an allowed restriction, restoration or escalation under the approved policy. Group moderation does not change a person’s paid entitlement or platform-wide role.

What to check in the demo

Follow these steps from the role’s landing page through navigation and feature checks.

Review as

Group moderator

Start here: Home

Choose the Morgan Ellis dummy account and open its assigned Group moderator Home without a password or authenticator prompt. This dev-only Home review does not verify MFA or unlock protected staff actions. Use your own provisioned staff account and authenticator when reviewing those actions.

Navigation from sign-in

  1. 01Open the fictional Group moderator account through the connected sign-in service. Seeded Home review opens directly. Real HOL staff access and protected actions require an authenticator check.
  2. 02On Group moderator Home, select Pending contributions to open the sample assigned-group queue.

Feature checks start here

Pending contributions and Reported content

A partial role preview is available. Group moderator → Pending contributions supports sample approval and rejection with a required reason; Reported content supports reasoned escalation. The sample queue is not connected to member contribution/report state or real scope enforcement. Review the current sample controls, then treat remaining checks as planned acceptance.

  1. 03On Pending contributions, select Approve for the first sample note and check its recorded sample status.
  2. 04Enter a review note for the second contribution, then select Reject with reason; check the recorded sample status.
  3. 05Return to Group moderator Home, open Reported content, enter a review note and select Escalate report.
  4. 06Remaining acceptance: connect these decisions to the member contribution/report state and demonstrate publication outcomes and enforced assigned-group scope.
  5. 07Once built, hide and restore a sample group contribution with a reason; compare the same object in member and moderator views.
  6. 08Review a participation restriction/restoration and an out-of-scope case; confirm group-only effect and escalation rather than a global penalty.

Backend work for this feature

Requirements only · Backend implementation on hold

What needs to be supported

  • Store assigned-group submission/report queues, publication state, moderation decisions/reasons, participation cases and reversible restrictions with actor/time/history.
  • Authorize only the assigned moderator and permitted action; reject another group’s IDs, reporter-identity leakage and platform-wide/entitlement changes.
  • Apply approve/reject/hide/restore and group participation restrictions atomically against the current version; preserve evidence and a member-visible outcome without publishing pending text prematurely.
  • Prepare duplicate/stale-decision, appeal/restore and interrupted-update recovery. Escalate cross-group/global cases through D079; no live enforcement or notification is enabled while backend work is held.

How to verify when implementation is approved

  1. Use moderators assigned to different groups, a contributor and unrelated reader to verify queue, report privacy and permitted actions.
  2. Race a contributor edit with review, repeat hide/restore and change participation eligibility; verify one consistent group state and unchanged membership.
  3. Escalate an out-of-scope report through D079 and confirm no wider access or real message is implied.

Before this can work

  • Choose the Morgan Ellis dummy account and open its assigned Group moderator Home without a password or authenticator prompt. This dev-only Home review does not verify MFA or unlock protected staff actions. Use your own provisioned staff account and authenticator when reviewing those actions.
  • HOL must approve content/participation actions, appeal/restore policy, assignment rules and evidence retention before connected enforcement.

No prerequisite story has been confirmed. The setup above describes the content or decisions needed.

Connected stories