Skip to main content
Scrump provides moderation commands for staff actions and records supported actions performed through Discord’s interface or other bots.

​
Moderation commands

Scrump also checks role hierarchy and its own Discord permissions before applying an action.

​
Configure the moderation log

1

Open Security

Open your server at scrumpbot.com, then select Security.
2

Choose a log channel

Under Moderation logging, select the private text channel where Scrump should post action summaries.
3

Review permissions

Resolve any missing-permission warning shown at the top of the page. Audit synchronization requires View Audit Log.
Every Scrump moderation command creates one log-channel message and one archive entry. Scrump correlates the Discord audit entry with the command so the same action is not recorded twice. Actions performed through Discord’s interface and supported actions from other bots are also archived. Their source is labeled so they can be filtered separately.

​
Moderation archive

Free servers can use the Discord log channel. Plus adds the searchable website archive and moderation analytics. The archive can be searched by target, moderator, action, source, date, and reason. Archive rows cannot be deleted by server users. A server manager can redact reason text; the redaction is itself recorded.

​
Custom target messages

Plus and Pro can customize the DM sent to a moderation target. Messages can be plain text or a Discord embed and support these variables: {user}, {server}, {action}, {reason}, {duration}, {expires}, and {moderator} The dashboard includes a live Discord preview. Invalid configurations fall back to Scrump’s default message. If the target cannot receive DMs, the moderation action still succeeds and the archive records the failed DM.