Network Ban Appeal

Overview

Network Ban Appeal lets a partner submit, edit, or resubmit an appeal for an active FPH-admin network ban. It shows the network ban details, the active partner submitting the appeal, the appeal reason, decision state, review notes, and appeal revision history.

This page does not lift a ban. It sends the request to FPH admin for review.

Dashboard route

• /reports/network-ban-appeal?entryId=:watchlistEntryId&incidentId=:incidentId

Inputs and controls

Input or control	What it changes	Before using it
entryId query parameter	Selects the network ban watchlist entry being appealed.	Required; navigate from Bans to avoid a missing ID.
incidentId query parameter	Provides linked incident context when available.	Useful for traceability but entryId is the required lookup.
Back to Bans	Returns to /reports/bans.	Use when the wrong network ban is loaded.
Network ban details card	Shows subject, report ref, issuing org, and active partner submitting the appeal.	Confirm the active partner is the intended appellant.
Admin note	Explains that FPH admin manages network bans.	Read before submitting.
Reason for appeal	Markdown-ext field for a new appeal.	Be specific, factual, and include corrective steps or new evidence.
Submit appeal	Creates a pending appeal for FPH admin review.	Confirm the network ban is active and partner scope is correct.
Pending appeal view	Shows submitted reason and submitted/updated timestamp.	Use it as the current appeal record.
Edit	Opens the pending appeal edit form.	Use before FPH admin decides the appeal.
Update appeal	Saves a revised pending appeal reason.	This writes appeal revision history.
Cancel edit	Closes the pending appeal edit form.	Use when no changes should be saved.
Appeal decision card	Shows approved or denied decision, submitted date, reason, and review notes.	Use as final decision evidence.
Updated reason	Markdown-ext field shown after denial.	Add new context, not just the same request.
Resubmit appeal	Reopens a denied appeal for review with the updated reason.	Only resubmit when there is new or clearer information.
Revision history	Shows previous and changed appeal reasons.	Use to audit appeal edits and resubmissions.

Workflow

flowchart TD
  bans["Open Bans network row"] --> appeal["Open Network Ban Appeal"]
  appeal --> active{"Network ban active?"}
  active -- No --> error["Show cannot appeal"]
  active -- Yes --> existing{"Appeal exists?"}
  existing -- No --> create["Enter reason and submit"]
  existing -- Pending --> edit["View or update pending reason"]
  existing -- Approved --> finalA["Show approved decision"]
  existing -- Denied --> resubmit["Update reason and resubmit"]
  create --> pending["Pending FPH-admin review"]
  edit --> pending
  resubmit --> pending
  pending --> admin["FPH admin reviews appeal"]
  admin --> finalA
  admin --> finalD["Show denied decision"]
  click admin "./ban-appeals/" "Open Ban Appeals docs"

State behavior

State	What happens
Missing entryId	Error section says no watchlist entry ID was provided.
No active partner	Error asks the user to select a partner.
Network ban inactive and no appeal exists	Error says the ban cannot be appealed.
Existing pending appeal	Pending view appears with Edit.
Approved appeal	Decision card appears without resubmit form.
Denied appeal	Decision card and Update and resubmit form appear.
Appeal revisions exist	Revision history card appears.

Related pages

• Bans for the entry point.
• Ban Appeals for FPH-admin review.
• Appeal Lifecycle for state meaning.

End-to-end operator runbook

1. Start from Bans: Use the network-ban row so entryId is correct.
2. Confirm appellant: Check the Appealing as partner label.
3. Write reason: Explain facts, evidence, corrective steps, or why the ban should be reconsidered.
4. Submit or update: Save the appeal and verify it returns as pending.
5. Track decision: Return after FPH review to read decision status and review notes.

Common mistakes

Do not submit an appeal under the wrong active partner. The appeal is tied to the current partner scope, not just the logged-in user.