Automatic does not mean uncontrolled
Stoatmod checks text and qualifying images against the moderation categories a server enables. A category only triggers when its score is greater than the effective threshold and its configured action permits an intervention.
Policy Studio separates observation from enforcement. Teams can watch matches first, move selected categories into review and enable stronger actions only after they understand the effect on their own community.
- Observe matches without taking action.
- Send selected matches for moderator review.
- Delete, warn or time out according to each category policy.
- Keep channel exclusions and moderator exemption under server control.
Thresholds and category policy
The default moderation threshold is 90%. The dashboard limits normal policy thresholds to 50–100%. The legacy command permits lower values only after a separate confirmation because low thresholds can act on weak background scores.
~thresholdShow the current threshold.
~threshold set 90Set a 90% threshold.
~categoriesReview enabled moderation categories.
Safety and failure behaviour
- Moderation-provider or network failures are fail-open, so the message remains rather than being silently removed.
- Suicidal thoughts use an always-enabled supportive DM category without deleting or warning. Promoting self-harm is a separate moderation category.
- Moderator exemption is enabled by default and can be changed by the server team.
- Cases and event history provide review context, but not every operational event becomes a moderation case.
Recommended rollout
- 01
Audit permissions
Run setup and resolve missing permissions or role hierarchy first.
~setup - 02
Review current policy
Open the dashboard or inspect categories and threshold commands before changing anything.
- 03
Start conservatively
Use observe or review modes for uncertain categories and keep the 90% default while testing.
- 04
Verify the outcome
Confirm the expected message, warning, timeout and case behaviour in a controlled channel.