Report System

Overview

The Report System is the partner dashboard area for formal safety records. It covers intake, review, evidence, local watchlists, local bans, network ban recommendations, appeals, and identity grouping through person profiles.

Use these docs as operator references. Each surface page names the dashboard route, every visible input or control, the records affected, the workflow around the page, and common mistakes.

Primary surfaces

Surface	Route	Use it for
Reports Overview	/reports	Counts, reminders, and recent activity.
All Reports	/reports/all	Search across visible incident reports and local ban shortcuts.
My Reports	/reports/my-reports	Current organization’s reports and open reminders.
New Report	/reports/new	Formal incident intake.
Report Detail	/reports/detail?id=:incidentId	Read-only source evidence and revision history.
Manage Report	/reports/manage?id=:incidentId	Edits, status changes, actions, evidence, and revision capture.
Watchlists	/reports/watchlists	Local and shared watchlist context.
Bans	/reports/bans	Local bans, network bans, and appeal entry points.
Cross-ban Requests	/reports/cross-bans	FPH-admin network-ban recommendation review.
Person Profiles	/reports/profiles	Group related reports by identity signals.

System workflow

flowchart TD
  intake["New Report"] --> detail["Report Detail"]
  detail --> manage["Manage Report"]
  manage --> local{"Local action type"}
  local --> watchlist["Watchlist"]
  local --> ban["Local ban"]
  manage --> cross{"Cross-community recommendation?"}
  cross -- Yes --> fph["FPH-admin Cross-ban Requests"]
  fph --> network["Network ban or denial"]
  network --> appeal["Network Ban Appeal"]
  detail --> profiles["Person Profiles"]
  click intake "./surfaces/new-report/" "Open New Report docs"
  click detail "./surfaces/report-detail/" "Open Report Detail docs"
  click manage "./surfaces/manage-report/" "Open Manage Report docs"
  click fph "./surfaces/cross-bans/" "Open Cross-ban Requests docs"
  click appeal "./surfaces/network-ban-appeal/" "Open Network Ban Appeal docs"
  click profiles "./surfaces/person-profiles/" "Open Person Profiles docs"

Inputs and controls to inspect first

Control family	Where documented	Why it matters
Status, severity, evidence, people, action, ban scope, appeal, signature	New Report and Manage Report	These fields create and maintain the safety record.
Search, status filters, row actions, detail links	All Reports and My Reports	These decide which record an operator opens or edits.
Local and network restriction controls	Bans and Report Detail	These can affect community access and event registration.
Network decision and appeal review controls	Cross-ban Requests and Ban Appeals	These are FPH-admin actions with network impact.
Identity grouping controls	Person Profiles	These link reports without changing report facts.

End-to-end operator runbook

1. Start with route map: Use Report System Route Map when a handoff names a dashboard route.
2. Open the record: Use Detail before making any safety or restriction decision.
3. Edit deliberately: Use Manage Report for durable facts, action notes, and appeal wording.
4. Separate scopes: Keep local watchlist/ban work separate from FPH-admin network-ban work.
5. Verify history: Check revision history, appeal history, and profile audit logs after changes.

Common mistakes

Do not treat the report system as a single list. Intake, local action, network review, appeals, and identity grouping are separate workflows with different permissions and evidence requirements.