Moderate your community
Choose the least disruptive action
Section titled “Choose the least disruptive action”| Situation | Action | Durable effect |
|---|---|---|
| Immediate disruption | Kick | Disconnects; user may return |
| Temporary posting restriction | Timeout | Blocks message activity for a duration |
| Ongoing exclusion | Ban | Adds banned, disconnects, denies future auth |
| Harmful content | Delete message | Removes record and referenced attachments |
| Identity cleanup | Update nickname | Changes server-local presentation |
Always provide a useful reason. Moderation actions against the owner are blocked.
Reports
Section titled “Reports”Give trusted moderators review_reports. Establish who checks open reports, what evidence is recorded, and when a report is resolved. Report review and user management are separate permissions so triage can be delegated without granting ban/kick access.
Audit review
Section titled “Audit review”Give oversight staff view_audit_log. Review user moderation, role management, channel management, message moderation, and server management categories. Configure retention long enough for your governance needs and export/back up records before expiry when policy requires it.
The configuration schema currently includes automod word-list and timeout settings, but no message-processing path reads or enforces them. Treat those fields as reserved until enforcement is implemented; they do not presently protect a server.