Report Detail

Overview

Report Detail is the source view for one incident report. It renders the report number, subject, badges, summary, details, people, violations, witnesses, actions, sharing fields, reporting officer, network-ban notice, and revision history.

Use this page before changing status, adding a ban, reviewing an appeal, or handing a case to another person.

Dashboard route

• /reports/detail?id=:incidentId

Inputs and controls

Input or control	What it changes	Before using it
id query parameter	Chooses which incident report to load.	Confirm the report title and number after load.
Back	Returns to All Reports.	Use when the report ID is wrong or the case does not need action.
Edit report	Opens /reports/manage?id=:incidentId when the user has edit rights.	Use for field edits only after reading the current evidence.
Add to ban list	Opens ban scope modal when the report is not already locally banned and not a network ban.	Confirm evidence, action notes, and appeal process first.
Edit ban	Opens edit-ban modal for an existing local ban.	Use when the ban scope or existence needs correction.
Request appeal	Appears on active network-ban notice. Opens /reports/network-ban-appeal?entryId=:entryId&incidentId=:incidentId.	Use when the current partner is requesting FPH review of a network ban.
Select ban scope: Community ban	Adds or keeps a local community-only ban.	Does not block event registration.
Select ban scope: Community + events ban	Adds or keeps a local event-impacting ban.	Treat as a serious action; it can block event registration.
Remove ban	Removes the local ban action type and returns the report to watchlist local action.	Explain the reason in Manage Report if context changed.
Save / Add ban / Cancel in modals	Applies or dismisses the selected ban change.	Cancel if the report or scope is uncertain.

Read-only sections

Section	What it shows	How to use it
Header badges	Severity, status, partner, cross-ban recommendation, and network-ban state.	Verify lifecycle and network impact quickly.
Summary	Markdown-rendered short case summary.	Use it for orientation, not complete evidence.
Details	Report ref, filed time, occurred time, event, platform, platform detail, org type, and last updated.	Confirm chronology and scope.
Reported person	Names, handle, email, alt handles, location, and standing.	Check identity carefully before restrictions.
Victim	Names, handle/contact, relation, statement, and evidence submitted.	Protect sensitive identity.
Violations	Violation chips, detail, prior history, and evidence.	Compare categories with narrative evidence.
Witnesses	Witness names, contacts, and notes.	Use for follow-up, not broad sharing.
Actions taken	Action types, local action, dates, end time, ban duration, appeal process, and action notes.	This is the restriction rationale.
Sharing	Shared organizations, cross-ban recommendation, and cross notes.	Use to understand network-review context.
Reporting officer	Officer name, role, contact, and email.	Confirms who filed the report.
Revision history	Revision number, change kind, actor email, date, and changed fields.	Use to audit edits after submission.

Workflow

flowchart TD
  open["Open /reports/detail?id=:incidentId"] --> loaded{"Report found in scope?"}
  loaded -- No --> error["Show no report or missing ID error"]
  loaded -- Yes --> read["Read badges, sections, and revision history"]
  read --> network{"Active network ban?"}
  network -- Yes --> appeal["Request network ban appeal"]
  network -- No --> local{"Needs local ban action?"}
  local -- Yes --> scope["Choose or edit local ban scope"]
  local -- No --> edit{"Needs content update?"}
  scope --> verify["Verify updated ban button"]
  edit -- Yes --> manage["Open Manage Report"]
  edit -- No --> handoff["Record report number and status"]
  click appeal "./network-ban-appeal/" "Open Network Ban Appeal docs"
  click manage "./manage-report/" "Open Manage Report docs"

State behavior

State	What happens
No id query parameter	The page shows No report ID.
Report not visible in scope	The page shows Report not found.
User cannot edit	Edit report is hidden.
Active network ban	Local ban controls are hidden; appeal action may appear.
Markdown fields	Summary, statements, evidence, notes, and appeal process render as sanitized markdown.
Revision history exists	A revision table appears at the bottom of the page.

Related pages

• Manage Report for editing.
• Network Ban Appeal for partner appeal submission.
• Evidence Handling for safe link and screenshot practices.

End-to-end operator runbook

1. Verify identity: Confirm report number, subject, partner, status, and severity.
2. Read evidence: Review detail, people, violation, witness, and action sections.
3. Check provenance: Review reporting officer and revision history.
4. Choose action: Edit, add/edit local ban, request network appeal, or hand off.
5. Document handoff: Share report number, current state, and next owner.

Common mistakes

Do not rely on the summary alone. The decision record lives across the evidence fields, action notes, appeal process, and revision history.