Furries PH Docs
Dashboard
Report system docs

Surfaces

Ban Appeals

FPH-admin review surface for network ban appeals by network ban entry.

First created Last updated

reportsban-appealsfph-adminappeals

Overview

Ban Appeals is the FPH-admin detail page for a specific network ban entry and its submitted partner appeals. It shows the network ban subject, scope, status, linked report, each appeal reason, edit history, review notes, and decision controls.

This page is restricted to FPH admins.

Dashboard route

  • /reports/ban-appeals?entryId=:watchlistEntryId

Inputs and controls

Input or controlWhat it changesBefore using it
entryId query parameterSelects the network ban entry and appeal list.Required; open from Bans or Cross-ban Requests.
Back to BansReturns to /reports/bans.Use when the wrong entry is loaded.
Access denied stateAppears for non-FPH-admin users.Do not route appeal decisions around this restriction.
No entry stateAppears when entryId is missing.Navigate from an entry row.
Network ban detailsShows scope, status, and linked report.Confirm subject and scope before deciding appeals.
View reportOpens Report Detail for the linked incident.Use to read source evidence before deciding.
Appeal rowShows status, submitting partner, reason, update marker, review notes, edit history, and submitted time.Compare reason with source report and network decision.
ApproveOpens review modal with an approved decision.Approval means the appeal succeeds and the ban should be lifted according to API behavior.
DenyOpens review modal with a denied decision.Use only with a clear reason.
Review notesOptional markdown-ext notes shared with the partner.Keep notes factual and decision-focused.
Approve - lift banSelects approve in the modal.Confirm the correct appeal and entry.
Deny appealSelects deny in the modal.Add review notes when denial needs explanation.
Confirm decisionWrites the selected appeal decision.This is the audit point; do not click until reviewed.
CancelCloses the modal without saving.Use if more review is needed.

Workflow

flowchart TD
  entry["Open /reports/ban-appeals?entryId"] --> access{"FPH admin?"}
  access -- No --> denied["Show access denied"]
  access -- Yes --> details["Load network ban details and appeals"]
  details --> report["Open source Report Detail"]
  report --> review["Read appeal reason and revisions"]
  review --> decision{"Decision"}
  decision -- Approve --> approve["Approve - lift ban"]
  decision -- Deny --> deny["Deny appeal"]
  approve --> notes["Add optional review notes"]
  deny --> notes
  notes --> confirm["Confirm decision"]
  confirm --> reload["Reload appeal list"]
  click report "./report-detail/" "Open Report Detail docs"

State behavior

StateWhat happens
Not FPH adminAccess denied alert is shown and content is hidden.
Missing entryIdNo entry ID alert is shown.
No appealsAppeals list shows No appeals submitted for this ban yet.
Pending appealApprove and Deny buttons are shown.
Decided appealDecision badge and review notes are shown; decision buttons are hidden.
Edited appealUpdated badge and edit history appear.

End-to-end operator runbook

  1. Confirm access and entry: Verify FPH-admin access and the loaded network ban subject.
  2. Read source report: Open the linked report before deciding.
  3. Review appeal text: Check reason, revisions, submitting partner, and prior review notes.
  4. Decide: Choose approve or deny and add concise notes.
  5. Verify reload: Confirm the appeal row shows the final status and notes.

Common mistakes

Do not decide an appeal from the appeal reason alone. The source report and network-ban scope must be reviewed before approval or denial.

All docs