Report System Route Map

Overview

Use this route map when a handoff, bug report, or support request names a Report System URL. Query parameters matter: id selects an incident report, and entryId selects a network-ban watchlist entry.

Route map

Route	Purpose	Docs page
/reports	Overview metrics, reminders, recent reports, recent bans, recent updates.	Reports Overview
/reports/all	All visible incident reports with search, status filter, detail/manage links, and local ban shortcuts.	All Reports
/reports/my-reports	Current organization’s report queue with reminders, search, and status filter.	My Reports
/reports/mine	Legacy grouped My Reports compatibility route.	Mine Compatibility
/reports/new	New report intake form.	New Report
/reports/detail?id=:incidentId	Read-only single-report evidence and revision view.	Report Detail
/reports/manage?id=:incidentId	Editable report form for status, evidence, people, action, ban, appeal, and cross-ban fields.	Manage Report
/reports/watchlists	Local and shared non-ban watchlist entries.	Watchlists
/reports/bans	Local bans, network bans, and active appeal entry points.	Bans
/reports/ban-appeals?entryId=:watchlistEntryId	FPH-admin network-ban appeal review for a selected entry.	Ban Appeals
/reports/cross-bans	FPH-admin cross-community ban recommendations and appeal queue.	Cross-ban Requests
/reports/network-ban-appeal?entryId=:watchlistEntryId&incidentId=:incidentId	Partner-facing network-ban appeal submission and status page.	Network Ban Appeal
/reports/profiles	Person profiles, report linking, detected similar reports, and audit log.	Person Profiles

Query parameter rules

Parameter	Used by	Rule
id=:incidentId	Detail and Manage Report	Must identify a report visible in the user’s scope.
entryId=:watchlistEntryId	Network Ban Appeal and Ban Appeals	Must identify a network-ban watchlist entry.
incidentId=:incidentId	Network Ban Appeal	Adds linked report context; entryId remains the required appeal lookup.

Inputs and controls to verify

Route family	Inputs or controls
Report list routes	Search fields, status filters, row action menus, detail/manage links, local ban modals.
Report record routes	id query parameter, back links, edit links, save/revert controls, local ban controls.
Appeal routes	entryId query parameter, reason fields, review notes, approve/deny buttons, confirm decision.
FPH-admin routes	Pending/decided/all/appeals tabs, access-denied state, network scope radios, required reason.
Profile route	Profile form fields, detected suggestions, report picker search, link/unlink/delete controls.

Workflow

flowchart TD
  handoff["Handoff includes route"] --> identify{"Has query parameter?"}
  identify -- id --> incident["Open Detail or Manage and verify report number"]
  identify -- entryId --> entry["Open appeal route and verify network ban subject"]
  identify -- none --> list["Open list or overview route"]
  incident --> proof["Use matching surface docs"]
  entry --> proof
  list --> proof

End-to-end operator runbook

1. Copy exact route: Keep path and query parameter together.
2. Name record: Include report number or network-ban subject in the handoff.
3. Open matching docs: Use the docs page in the table above.
4. Verify loaded state: Check title, badges, partner, and entry status after load.
5. Avoid stale links: Reopen from list pages when a copied URL does not match the expected record.

Common mistakes

Do not send /reports/manage or /reports/detail without the id query parameter. The path alone does not identify the report.