Watchlist and Alerts
Review Watchlist alerts, scheduled follow-up, and authorized sources before choosing an explicit next action.
- Audience
- moderator · senior reviewer · team lead
- Availability
- premium preview · feature flagged
- Maturity
- beta · partial
Last reviewed
On this page
What the Watchlist includes
Watchlist records can include a reason, reviewer, next review, expiry, alerts, human notes, authorized source references, observed activity, audit history, No Contact relationships, and Ban Warnings. The Dashboard is the in-depth workspace; `/watchlist open` provides the compact routine Discord workflow over the same canonical records.
Review a signal before acting
Open the source
Read the observed event, affected member, time, source availability, data quality, watch reason, owner, and linked Case context available to your role.
Check: You can identify what was observed, what is missing, and what is restricted before choosing an action.
Check the current work
Keep the alert or due review separate from lifecycle, ownership, and historical context. Do not turn repeated signals into an unsupported factual claim.
Check: The next action follows the current record and permission state rather than a score.
Set outcome
Acknowledge, assign, snooze, complete a review, resolve with no follow-up, or close as a false positive. Start a Case only through the explicit permission-gated handoff.
Check: The audit identifies the reviewer, reason, time, and resulting state without automatic punishment or workflow creation.
Protect relationship and destination data
| Record | Limit or safeguard |
|---|---|
| Membership and alerts | Internal review data; use staff-only destinations and expire or correct stale entries. |
| Sources and review state | Show observed records before interpretation; missing or restricted source data remains explicit. |
| No Contact relationship | Sensitive pair data; restrict visibility and explain any voice-separation behavior in server notices. |
| Auto-ban option | Separate double-gated authority and not the default Watchlist outcome. |
An alert is missing, repeated, or visible in the wrong place
What you see: An alert does not arrive, appears more than once, looks stale, or reaches a destination with unexpected access.
What may be happening: Module state, source visibility, alert gates, snooze state, Discord permissions, destination routing, or delivery failure can change the result.
What to do
- Do not act until the original source and destination permissions are verified.
- Check acknowledgement, snooze, expiry, reviewer, and false-positive history before creating or reporting a duplicate.
- Move sensitive discussion to an approved private Case or the separately configured Ban Warning and Ban Review workflow, then report routing exposure to an administrator.