Skip to main content
Every moderation action you take through Newt — a ban, a kick, a timeout, a warning, a freeze, an imageban — becomes a numbered case in a persistent log. That case records who carried out the action, who it was carried out against, when it happened, how long it lasts, and why. You can browse cases, read them individually, edit their reasons, and build up a complete picture of moderation history that stays put even after members leave.

Set Up the Moderation Log

Run /logging moderation and pick a channel. From then on, every action posts there with its case number and full details. Actions still work and are still recorded if you skip this step — they just aren’t posted anywhere visible.

Permission Model

Who can use moderation commands is set on the dashboard’s Permissions tab, not by Discord permissions alone. Someone with the Ban Members permission in Discord still can’t run /ban until their role is allowed on the Permissions tab. The server owner, Administrators, and any roles you explicitly whitelist can always use moderation commands. For the bot to action someone, its role must sit above that person in the role hierarchy. Go to Server Settings → Roles and drag the bot’s role above anyone you want it to be able to action. You can’t action someone whose top role is at or above your own, and no one can action the server owner.

Duration Format

Write durations naturally: 10m, 2h, 1d, 1h30m. Discord caps timeouts at 28 days.

About Warnings

/warn remove marks a warning inactive — it stops counting toward a member’s total — but it stays visible in /case list. Removing a warning never quietly erases the trail.

Commands

Bans & Kicks

Timeouts

Warnings

Imageban

Freeze

Cases & Notes

Channel Control

Ticket Bans

Ticket bans prevent a member from opening new support tickets. Their existing open tickets stay open.