Cross-ban Requests

Overview

Cross-ban Requests is the FPH-admin queue for reports where a partner recommended network review. It separates pending recommendations, decided recommendations, all recommendations, and network-ban appeals.

Approving a recommendation can create a network ban with a chosen network scope. Denying records the decision reason without creating a network ban.

Dashboard route

• /reports/cross-bans

Inputs and controls

Input or control	What it changes	Before using it
Access denied state	Hides queue content from non-FPH-admin users.	Use FPH-admin account for network decisions.
Pending review tab	Shows cross-ban recommendations without a decision.	Default queue for action.
Decided tab	Shows recommendations with approved or denied decisions.	Use for audit and corrections.
All tab	Shows all cross-ban recommendations.	Use for search across states.
Ban appeals tab	Shows network-ban appeals inside the same admin workflow.	Use Details to open the appeal entry page.
Appeals badge	Shows pending appeal count.	Treat as review queue signal.
Search in request table	Filters by subject, ref, severity, org, summary, recommendation, notes, or decision.	Clear search before declaring the queue empty.
Search in appeals table	Filters by subject, ref, status, partner, reason, or notes.	Search does not change records.
Details	Opens Report Detail for the report.	Always review evidence before deciding.
Appeals	Opens Ban Appeals when a network-ban entry is associated.	Use for appeal review.
Approve	Opens decision modal with approved decision selected.	Confirm evidence and choose network ban scope.
Deny	Opens decision modal with denied decision selected.	Add a required reason.
Actions on decided row	Opens modal to edit an existing decision.	Use only when correcting an admin decision.
Ban scope: Community spaces and events	Network ban blocks community spaces and events.	Strongest network action; verify event-rego impact.
Ban scope: Community spaces only	Network ban applies only to community spaces.	Use when event-rego blocking is not justified.
Reason	Required decision reason.	Write factual admin rationale.
Confirm decision	Saves approved or denied decision.	This is the network audit point.
Cancel	Closes decision modal without saving.	Use if more review is needed.

Table fields

Column	Meaning
Ref	Report number for source trace.
Subject	Reported person label.
Severity	Source report urgency.
Decision	Pending, approved, or denied.
Partner	Recommending partner organization.
Context	Recommendation text, cross notes, prior decision, and decision reason.
Filed / Submitted	Filing or appeal submission time.
Actions	Detail, appeal, approve, deny, or edit decision actions.

Workflow

flowchart TD
  queue["Open Cross-ban Requests"] --> access{"FPH admin?"}
  access -- No --> denied["Show access denied"]
  access -- Yes --> tab["Choose pending, decided, all, or appeals"]
  tab --> detail["Open Report Detail"]
  detail --> decide{"Network decision"}
  decide -- Approve --> scope["Choose community-only or community + events"]
  decide -- Deny --> reason["Write denial reason"]
  scope --> reason
  reason --> confirm["Confirm decision"]
  confirm --> network["API records decision and network-ban state"]
  tab --> appeals["Open appeal details"]
  click detail "./report-detail/" "Open Report Detail docs"
  click appeals "./ban-appeals/" "Open Ban Appeals docs"

State behavior

State	What happens
Not FPH admin	Access denied alert is shown.
No pending recommendations	Pending tab shows an empty state.
No search match	Table shows no matching requests or appeals.
Approved selected	Scope radio group appears in the decision modal.
Denied selected	Scope row is hidden because no network ban scope is needed.
Missing reason	Save stops and modal error asks for a reason.
Decision saved	Queue reloads and row moves to decided state.

Related pages

• Report Detail for source evidence.
• Ban Appeals for network appeal review.
• Local vs Network Records for scope meaning.

End-to-end operator runbook

1. Open pending queue: Start on Pending review unless auditing older decisions.
2. Read source report: Open Detail and review evidence, action notes, and appeal process.
3. Choose decision: Approve only when the case justifies network action; otherwise deny with reason.
4. Set scope: For approval, pick community-only or community-and-events based on risk.
5. Verify audit: Confirm the row shows decision, reason, scope, and decision time.

Common mistakes

Do not approve a network ban because a partner checked the recommendation box. The checkbox is a request for FPH-admin review, not an automatic network action.