Local vs Network Records

Overview

Local records belong to a partner’s operational scope. Network records are reviewed or managed by FPH admin and can affect multiple partners. Mixing those scopes is the fastest way to make a bad safety decision.

Use the route and badge names to identify who owns the next action.

Scope model

flowchart TD
  report["Partner incident report"] --> localWatch["Local watchlist"]
  report --> localBan["Local ban"]
  report --> recommend["Cross-community recommendation"]
  recommend --> fph["FPH-admin review"]
  fph --> networkBan["Network ban"]
  networkBan --> partnerAppeal["Partner appeal"]
  partnerAppeal --> fphAppeal["FPH-admin appeal decision"]

Inputs and controls by scope

Scope	Controls	Surface	Owner
Local watchlist	Furries PH action type = Watchlist, watchlist rows, local entries	New Report, Manage Report, Watchlists	Partner with report edit rights.
Local community ban	Furries PH action type = Ban, ban scope = community spaces only, edit ban modal	Manage Report, Bans	Partner with report edit rights.
Local community + events ban	Furries PH action type = Ban, ban scope = events and community, edit ban modal	Manage Report, Bans	Partner with report edit rights; affects event registration.
Cross-community recommendation	Recommend cross-community ban checkbox and cross notes	New Report, Manage Report	Partner recommends; FPH admin decides.
Network ban	Approve cross-ban decision, network ban scope, decision reason	Cross-ban Requests	FPH admin.
Network ban appeal	Appeal reason, review notes, approve/deny appeal	Network Ban Appeal, Ban Appeals	Partner submits; FPH admin decides.

Workflow

flowchart TD
  local["Local action needed"] --> watchOrBan{"Monitoring or restriction?"}
  watchOrBan -- Monitoring --> watch["Set Watchlist"]
  watchOrBan -- Restriction --> scope{"Blocks events?"}
  scope -- No --> community["Community-only ban"]
  scope -- Yes --> events["Community + events ban"]
  events --> recommend{"Network impact needed?"}
  community --> recommend
  recommend -- Yes --> fph["Cross-ban Requests"]
  recommend -- No --> localDone["Local record remains local"]

End-to-end operator runbook

1. Find ownership: Identify whether the row is local, shared, or network-managed.
2. Read source report: Use Detail to confirm action notes and appeal process.
3. Pick the narrow scope: Use watchlist, community ban, event-impacting ban, or network recommendation based on evidence.
4. Route network work: Send network decisions and appeals through FPH-admin pages.
5. Record handoff: Include scope, owner, report number, and next decision point.

Common mistakes

Do not use a local ban edit to handle a network ban. Local controls affect partner records; network bans require FPH-admin decision or appeal review.