Furries PH Docs
Dashboard
Report system docs

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

TermMeaning
Incident reportFormal safety record created from New Report and maintained through Manage Report.
Report numberHuman-readable reference used in handoffs and tables.
SeverityUrgency label: low, medium, high, or critical.
StatusLifecycle state: new, triage, investigating, resolved, or closed.
Open reportReport with New, Triage, or Investigating status.
WatchlistLocal or shared monitoring record that is not a formal ban.
Local banPartner-owned restriction recorded through report action fields.
Community banLocal ban from community spaces only; does not block event registration.
Community + events banLocal or network restriction that can block event registration.
Network banFPH-admin-managed ban visible across partners according to network scope.
Cross-community ban recommendationPartner request for FPH-admin network-ban review.
Cross-ban decisionFPH-admin approval or denial of a cross-community recommendation.
Network ban appealPartner request for FPH-admin review of an active network ban.
Appeal revisionHistory of changed appeal reasons.
Person profileIdentity grouping record that links reports by names, handles, emails, or other signals.
Profile linkConnection between a person profile and an incident report.
Revision historyAudit trail of report edits after creation.
Action notesMarkdown field explaining what staff did and why.
Appeal processMarkdown field explaining how the subject can request review.
FPH adminRole allowed to decide cross-ban recommendations and network-ban appeals.

Inputs and controls referenced by terms

Term familyMain surfaces
Report intake and statusNew Report, Manage Report
Watchlist and local bansWatchlists, Bans
Network bans and appealsCross-ban Requests, Network Ban Appeal, Ban Appeals
Profiles and identity linksPerson Profiles

End-to-end operator runbook

  1. Find the term: Use the table before acting on unfamiliar report wording.
  2. Open the surface: Follow the linked surface docs for controls and route behavior.
  3. Confirm scope: Check whether the term is local, shared, or network-managed.
  4. Verify source: Use Report Detail or the relevant appeal/profile page for proof.
  5. 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.

All docs