All Reports

Overview

All Reports is the broad report list for the current user’s visible scope. It is the right page when an operator knows a report exists but does not know whether it belongs to their organization, another visible partner, or a network decision.

The page can open details, open the manage form when the user has edit rights, add a local ban, edit a local ban, or remove a local ban. It cannot change the body of a report directly; those edits happen in Manage Report.

Dashboard route

• /reports/all

Inputs and controls

Input or control	What it changes	Before using it
Search	Filters visible rows by report number, subject name, handle, real name, email, status, severity, partner, or summary.	Search does not change records; clear it before concluding a report is missing.
Status filter	Filters rows by All statuses, Open, Resolved, or Closed. Open includes New, Triage, and Investigating.	Confirm the selected filter before reporting counts.
Details	Opens /reports/detail?id=:incidentId.	Use this before acting on a report.
Actions menu	Opens row actions for the selected report.	Confirm the row subject and report number.
Open details	Same as Details.	Use for read-only verification.
Manage report	Opens /reports/manage?id=:incidentId when the user can edit the report.	Edit rights depend on partner membership, filed-by ownership, and FPH role.
Add local ban	Opens the ban scope modal and then patches the report action record.	Confirm action notes and appeal process are already strong enough for a ban.
Edit ban	Opens the edit-ban modal for a local ban.	Use when the scope is wrong or the ban should be removed.
Select ban scope: Community ban	Creates or keeps a local community-spaces-only ban.	Use when event registration should not be blocked.
Select ban scope: Community + events ban	Creates or keeps a local ban that blocks community spaces and events.	Use only after team review; this affects event registration.
Remove ban	Removes local ban action type and returns the local action type to watchlist.	Keep the report status and notes aligned with the reason for removal.
Save / Add ban / Cancel in ban modals	Applies or dismisses ban-scope changes.	Cancel if the selected report or scope is uncertain.

Row fields

Column	Meaning
Ref	The report number used in handoffs and revisions.
Subject	Primary subject label plus handle, real name, or email when available.
Type	Network ban, local ban, watchlist, or blank. Network bans are managed by FPH admin.
Violations	Up to two violation category chips with a count for additional categories.
Severity	Low, medium, high, or critical urgency label.
Status	New, triage, investigating, resolved, or closed.
Filed	Filing time or creation time.
Partner	Originating partner organization visible to the current user.

Workflow

flowchart TD
  list["Open All Reports"] --> filter["Search or filter by status"]
  filter --> row["Pick the exact report number and subject"]
  row --> detail["Open Report Detail"]
  row --> canEdit{"User can edit?"}
  canEdit -- Yes --> manage["Open Manage Report"]
  canEdit -- No --> readOnly["Use Detail as read-only evidence"]
  row --> ban{"Need local ban update?"}
  ban -- Add --> scope["Choose community or community + events scope"]
  scope --> patch["Patch incident actions"]
  ban -- Edit/remove --> edit["Edit ban modal"]
  edit --> patch
  patch --> reload["Reload list and verify row type"]
  click detail "./report-detail/" "Open Report Detail docs"
  click manage "./manage-report/" "Open Manage Report docs"

Permission and state behavior

State	What happens
No incidents	The list shows No incidents for this scope.
No filter match	The list shows No reports match your filter.
Network ban row	Local ban controls are hidden because FPH admin manages the network ban.
Non-editable report	Manage Report is hidden from the row actions.
Load error	The card shows an error alert; retry before treating the list as empty.

Related pages

• Report Detail for source evidence.
• Manage Report for report edits and revision history.
• Bans for ban-only lists and active appeal links.

End-to-end operator runbook

1. Confirm scope: Verify the active partner and whether the work is local or network-level.
2. Find the row: Search by report number or subject, then clear filters if nothing appears.
3. Open proof: Use Details before applying an action.
4. Apply action: Use Manage Report for content edits or the ban modal for local ban scope changes.
5. Verify result: Reload the list and confirm the Type, Status, and Actions state.

Common mistakes

Do not add a local ban directly from a list search result if you have not opened the report evidence. The row is a shortcut, not the review record.