Reference
Report System Glossary
Definitions for report, watchlist, ban, network ban, appeal, profile, and revision terms used across the Report System docs.
First created Last updated
reportsglossaryreference
Overview
Use this glossary when a handoff or docs page uses Report System terms. Terms are written for operators, not database administrators.
Workflow map
flowchart LR report["Report"] --> revision["Revision"] report --> watchlist["Watchlist"] report --> ban["Ban"] ban --> network["Network ban"] network --> appeal["Appeal"] report --> profile["Person profile"]
Terms
| Term | Meaning |
|---|---|
| Incident report | Formal safety record created from New Report and maintained through Manage Report. |
| Report number | Human-readable reference used in handoffs and tables. |
| Severity | Urgency label: low, medium, high, or critical. |
| Status | Lifecycle state: new, triage, investigating, resolved, or closed. |
| Open report | Report with New, Triage, or Investigating status. |
| Watchlist | Local or shared monitoring record that is not a formal ban. |
| Local ban | Partner-owned restriction recorded through report action fields. |
| Community ban | Local ban from community spaces only; does not block event registration. |
| Community + events ban | Local or network restriction that can block event registration. |
| Network ban | FPH-admin-managed ban visible across partners according to network scope. |
| Cross-community ban recommendation | Partner request for FPH-admin network-ban review. |
| Cross-ban decision | FPH-admin approval or denial of a cross-community recommendation. |
| Network ban appeal | Partner request for FPH-admin review of an active network ban. |
| Appeal revision | History of changed appeal reasons. |
| Person profile | Identity grouping record that links reports by names, handles, emails, or other signals. |
| Profile link | Connection between a person profile and an incident report. |
| Revision history | Audit trail of report edits after creation. |
| Action notes | Markdown field explaining what staff did and why. |
| Appeal process | Markdown field explaining how the subject can request review. |
| FPH admin | Role allowed to decide cross-ban recommendations and network-ban appeals. |
Inputs and controls referenced by terms
| Term family | Main surfaces |
|---|---|
| Report intake and status | New Report, Manage Report |
| Watchlist and local bans | Watchlists, Bans |
| Network bans and appeals | Cross-ban Requests, Network Ban Appeal, Ban Appeals |
| Profiles and identity links | Person Profiles |
End-to-end operator runbook
- Find the term: Use the table before acting on unfamiliar report wording.
- Open the surface: Follow the linked surface docs for controls and route behavior.
- Confirm scope: Check whether the term is local, shared, or network-managed.
- Verify source: Use Report Detail or the relevant appeal/profile page for proof.
- Use exact wording: Put report number, status, scope, and role in handoffs.
Common mistakes
Do not use watchlist, ban, and network ban interchangeably. They represent different scopes, owners, and operational effects.