Local vs Network Records

Start With The Idea

Use this guide when a safety, accountability, or follow-up record needs careful handling. In this guide, Local vs Network Records narrows that work to understand which report records stay inside one partner and which can affect the shared Furries PH partner network. Because this is a foundations page, read it as part of the Report System learning path rather than as an isolated checklist.

A report is a written memory of something important. The goal is to protect people, keep facts clear, and leave enough context for future reviewers. Read the page for the decision it helps a person make, then use the steps and checks as a steady path from context to action to proof.

What This Page Explains

This is the concept layer. Read it before trying to operate the workflow so the later steps make sense in ordinary language first. The intended readers are Trust and Safety staff, Partner admins, and FPH administrators. If the guide names a dashboard route, service area, export, or record type, treat that name as a pointer to real operational responsibility.

• Primary surface or service: /reports/watchlists, /reports/cross-bans, and /reports/network-ban-appeal?entryId=:watchlistEntryId.
• Records or contracts involved: Local watchlist entries, Local bans, Network bans, and Cross-ban requests.
• Main care point: Watch for incomplete facts, unfair wording, privacy exposure, or a decision that another reviewer cannot understand later.
• Proof worth keeping: report ID, saved status, revision history, person profile, evidence note, reminder, reviewer decision, and handoff owner.

How The Idea Builds Toward Action

1. Say the idea in ordinary words: Begin by naming the Report System situation, the owner, and the exact item involved in Local vs Network Records.
2. Connect the idea to one real screen or source: Use /reports/watchlists, /reports/cross-bans, and /reports/network-ban-appeal?entryId=:watchlistEntryId to connect the words on the page to the screen, file, service route, or record that people actually use.
3. Name what could change for people or records: Keep Local watchlist entries, Local bans, Network bans, and Cross-ban requests in view so the work stays tied to the records or contracts it can affect.
4. Choose the next practical guide from the related links: Before handing off, save proof such as report ID, saved status, revision history, person profile, evidence note, reminder, reviewer decision, and handoff owner so another reviewer can understand the facts without relying on memory.

You Are Ready To Continue When

You are ready to use the rest of this page when the purpose, owner, affected information, and proof are all clear enough for a second person to review.

1. Scope is named: The work is tied to the correct page, event, report, route, file, person, or record.
2. Impact is understood: The operator can explain the effect on people, privacy, fairness, evidence, and the trustworthiness of the record.
3. Proof is findable: The handoff points to evidence that another reviewer can understand the facts without relying on memory.

End-to-end operator runbook

Use this numbered runbook when you need to operate this area without getting stuck. Read the purpose of each step, do the action in order, and use the final sentence as the checkpoint before continuing.

1. Step 1 - Choose the right path. Read this page before operating the related dashboard workflow so the terms and risks are clear. This anchors the work to the correct scope before any record changes.
2. Step 2 - Confirm scope and records. Identify which people, records, and community outcomes the workflow can affect. Pause here and confirm the note is factual, fair, and reviewable.
3. Step 3 - Do the operating action. Open /reports/watchlists, /reports/cross-bans, /reports/network-ban-appeal?entryId=:watchlistEntryId only when you know what decision or check you are performing. This keeps the report useful to the next reviewer instead of only to the person writing it.
4. Step 4 - Verify the result. Before changing Local watchlist entries, Local bans, Network bans, Cross-ban requests, ask whether the action is fair, accurate, necessary, and explainable later. The next action should still protect privacy, evidence, and due process.
5. Step 5 - Hand off remaining work. Use the related pages to move from concept to the exact operating surface, lifecycle, or reference checklist. This leaves a handoff trail another operator can understand.

Local records

A local record belongs to one partner. It helps that partner manage their own event or community space.

Examples:

• A local watchlist note.
• A ban from one partner’s event.
• A report only visible to that partner’s permitted staff.

Local does not mean unimportant. It only means the record is scoped to one partner.

Network records

A network record is shared across trusted Furries PH partners. It can affect whether a person is flagged or restricted beyond one partner.

Examples:

• Network ban.
• Shared network watchlist entry.
• Cross-community ban recommendation.
• Network ban appeal.

Quick comparison

Question	Local	Network
Who mainly uses it?	One partner’s staff.	Multiple partners and FPH admins.
Where does it appear?	Local report, local ban, local watchlist pages.	Shared watchlist, cross-ban, appeal pages.
Who decides?	Partner admins or trusted safety staff.	FPH admin or approved network workflow.
What is the risk?	Unfair impact inside one partner.	Unfair impact across communities.
What proof is needed?	Enough for partner action.	Stronger context and clearer action notes.

What to ask before network sharing

1. Question 1. Is there a clear safety reason other partners need to know? Write the answer before choosing the next action.
2. Question 2. Is the subject identified well enough to avoid mistaken identity? Write the answer before choosing the next action.
3. Question 3. Is evidence recorded, or only described vaguely? Write the answer before choosing the next action.
4. Question 4. Are action notes clear and fair? Write the answer before choosing the next action.
5. Question 5. Is there an appeal path? Write the answer before choosing the next action.