Your account
HOL-D079Story implementation: Planned

Resolve escalated community reports

community · Proposed launch phase 2

Start from Home

Review as Platform administrator · Full workflow planned

User story

As a platform administrator, I want to review cases explicitly escalated beyond group moderation so serious or cross-group issues receive an accountable scoped decision.

Draft requirements for review · Updated 2026-10-19

What the app should do

  • Show escalated cases with originating report/group, reason and minimum evidence; withhold reporter identity unless the approved policy permits access.
  • Record a review, request information, send back to the assigned moderator or resolve/escalate under an approved platform policy.
  • Any content restriction, account action or restoration needs explicitly assigned authority, a reason and a visible decision history; general administrator standing is not unlimited private-data access.
  • Separate case resolution, content visibility and account entitlement. Do not silently revoke paid access because a local review button was clicked.
  • Define appeal/retention/escalation responsibilities before connected enforcement. Use generalized fictional cases; no real moderation decision or external message occurs.

What to check in the demo

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

Review as

Platform administrator

Start here: Home

Choose the Robin Park dummy account and open its assigned Platform administrator 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 Platform administrator 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 Platform administrator Home, select Escalated cases.

Feature checks start here

Resolve escalated community reports · Full workflow planned

Planned full workflow. Existing workspace samples, where present, demonstrate only isolated controls. Backend implementation is on hold; no completed end-to-end outcome or stakeholder approval is claimed.

  1. 03Inspect the generalized sample escalation and Record review control; it does not enforce a real content or account restriction.
  2. 04Once built, trace a report from D027 through assigned-group moderation D026 into this escalated case.
  3. 05Request more information or apply an explicitly allowed resolution with a reason; inspect moderator/contributor-visible outcomes.
  4. 06Review a reversed/escalated decision and its history without exposing protected reporter or unrelated account data.

Backend work for this feature

Requirements only · Backend implementation on hold

What needs to be supported

  • Persist report/case references, originating scope, escalation reason, evidence access, assigned reviewer and versioned decisions/outcomes.
  • Enforce case-assigned administration and minimal evidence reads; separate any content-action/account-action capability from ordinary case review.
  • Apply approved content restriction/restoration atomically and audit actor/time/reason; membership changes require the separate authorized entitlement process.
  • Protect reporter identity and private evidence under the approved visibility/retention policy; support appeal/reversal rather than destructive evidence deletion.
  • Handle duplicate reports, conflicting resolutions, stale evidence and repeated restriction requests without duplicate or unauthorized actions.

How to verify when implementation is approved

  1. Trace a synthetic member report through group escalation; deny another moderator/admin without case authority access to protected evidence.
  2. Test approved resolution, reversal and repeated/stale decisions; verify consistent content state, audit history and unchanged unrelated membership.
  3. Verify reporter privacy and the contributor/moderator-visible outcome after reload; no live notification or account penalty is implied.

Before this can work

  • Choose the Robin Park dummy account and open its assigned Platform administrator 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.
  • Confirm platform escalation policy, case assignment, allowed content/account actions, appeal route and reporter/evidence retention before enforcement.
  • Use fictional role-preview records. Frontend prototypes may simulate the workflow; no backend implementation or real service operation is authorized.

Connected stories