Watchlists

Overview

Watchlists shows non-ban watchlist entries for the current partner scope and the shared network scope visible to the user. It is for monitoring, context, and follow-up. Formal bans appear on Bans.

The page does not create watchlist entries directly. Watchlist state is created from New Report, Manage Report, local action patches, or shared/adopted records.

Dashboard route

• /reports/watchlists

Inputs and controls

Input or control	What it changes	Before using it
Partner scope selector	Changes which local watchlist entries load.	Confirm scope before saying an entry is missing.
Local watchlist section	Shows non-ban watchlist entries owned by the active partner.	Use Detail to confirm the source report.
Shared network watchlist section	Shows non-ban shared entries from other visible partners.	Check originating org before sharing or acting.
Search in Local watchlist	Filters local rows by subject, ref, type, or severity.	Clear search before treating a section as empty.
Search in Shared network watchlist	Filters shared rows by subject, ref, type, severity, or partner.	Search affects only display.
Details	Opens /reports/detail?id=:incidentId for the linked report.	Use this before any handoff or adoption decision.

Row fields

Column	Meaning
Ref	Linked report number when the entry has a source report.
Subject	Watchlist summary and reported name.
Entry type	Watchlist-like type such as watchlist, warning, or warn. Ban-like types are excluded here.
Severity	Severity from the linked report when available.
Violations	Violation chips from the linked report.
Originating org	Partner that created the shared entry, shown in the shared section.
Actions	Detail link for the source report.

Workflow

flowchart TD
  open["Open Watchlists"] --> scope["Confirm partner scope"]
  scope --> local["Review local watchlist"]
  scope --> shared["Review shared network watchlist"]
  local --> detail["Open linked Report Detail"]
  shared --> origin["Confirm originating org"]
  origin --> detail
  detail --> action{"Needs formal restriction?"}
  action -- Yes --> manage["Open Manage Report or Bans"]
  action -- No --> handoff["Record monitoring context"]
  click detail "./report-detail/" "Open Report Detail docs"
  click manage "./manage-report/" "Open Manage Report docs"

State behavior

State	What happens
No entries	The section shows No entries.
No search match	The table shows No watchlist entries match the current search.
Entry has no linked report	The Ref and Details action may be blank.
Load error	Both sections can show an error alert.

Related pages

• Bans for formal restrictions.
• Local vs Network Records for scope meaning.
• Report Detail for source evidence.

End-to-end operator runbook

1. Confirm scope: Check whether the entry is local or shared.
2. Search carefully: Use subject, report ref, type, severity, or partner.
3. Open evidence: Use Details before acting.
4. Decide next step: Monitor, edit the source report, or escalate to a formal ban workflow.
5. Record handoff: Include source report number and whether the entry is local or shared.

Common mistakes

Do not treat watchlist presence as a ban. Watchlist means monitoring or retained safety context unless the report’s action fields say otherwise.