Bans

Overview

Bans separates formal restrictions into community bans, community-and-events bans, network bans, and the current partner’s active network-ban appeals. It is the safest place to review active restrictions without mixing them with non-ban watchlist entries.

Local bans can be edited from this page. Network bans are issued and reviewed by FPH admin; partners can request appeal from the network-ban row.

Dashboard route

• /reports/bans

Inputs and controls

Input or control	What it changes	Before using it
Partner scope selector	Changes local bans and current partner appeal context.	Confirm the active partner before editing a local ban.
My active ban appeals	Shows appeals submitted by the active partner when any exist.	Use Details to review or update appeal text.
Community bans section	Shows local bans that do not block event registration.	Open Detail before editing.
Community + events bans section	Shows local bans that can block event registration.	Treat edits as event-impacting.
Network bans section	Shows active FPH-admin network bans visible to the user.	Local edit controls do not apply.
Search	Filters rows by subject, ref, severity, partner, scope, duration, or appeal status depending on section.	Clear search before declaring a section empty.
Details	Opens Report Detail for the linked incident.	Use for evidence and action notes.
Actions menu on local bans	Opens Edit ban.	Confirm the row is local, not network-managed.
Edit ban	Opens the edit-ban modal.	Use to change scope or remove the local ban.
Edit ban modal: Community ban	Saves the local ban as community-only.	Does not block event registration.
Edit ban modal: Community + events ban	Saves the local ban as event-impacting.	Requires strong review because it can block event registration.
Remove ban	Removes local ban action type and returns local action to watchlist.	Update action notes in Manage Report if context changed.
View appeals	FPH-admin action on a network-ban row.	Opens the appeal review detail page.
Request appeal	Opens /reports/network-ban-appeal?entryId=:entryId&incidentId=:incidentId.	Use when the active partner is appealing a network ban.

Row fields

Column	Meaning
Ref	Linked report number.
Subject	Reported person name plus identity context.
Severity	Linked report severity.
Violations	Linked report violation chips.
Date	Local action date or record creation date.
Duration	Ban duration when available.
Partner / Originating org	Source partner for local or network record.
Ban type / Ban scope	Whether network restriction is community-only or community-and-events.
Appeal status	Pending, approved, or denied for the active partner’s appeals.

Workflow

flowchart TD
  bans["Open Bans"] --> section{"Which section?"}
  section --> local["Community or community + events"]
  section --> network["Network bans"]
  section --> appeals["My active appeals"]
  local --> detail["Open Report Detail"]
  detail --> edit["Edit ban scope or remove ban"]
  edit --> patch["Patch incident actions"]
  network --> appeal["Request network ban appeal"]
  appeals --> appealDetail["Open appeal details"]
  click detail "./report-detail/" "Open Report Detail docs"
  click appeal "./network-ban-appeal/" "Open Network Ban Appeal docs"

State behavior

State	What happens
No community bans	The section shows No community bans.
No community + events bans	The section shows No community + events bans.
No network bans	The section shows No network bans.
No search match	The relevant table shows no matching rows.
No active appeals	My active ban appeals card stays hidden.
FPH admin on network rows	View appeals appears when a network entry ID is available.

Related pages

• Network Ban Appeal for partner appeal submission.
• Ban Appeals for FPH-admin appeal review.
• Appeal Lifecycle for decision states.

End-to-end operator runbook

1. Classify restriction: Determine whether the row is local community-only, local event-impacting, or network-managed.
2. Open evidence: Review Report Detail before editing a local ban.
3. Apply local changes: Use Edit ban only for local rows.
4. Use appeal flow: Use Request appeal for network bans.
5. Verify list state: Reload or clear search and confirm the row moved or disappeared as expected.

Common mistakes

Do not try to remove a network ban by editing a local report. Network bans are FPH-admin records and must go through the appeal or cross-ban decision workflow.