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. Every command response is private to the moderator and names the action and target. Moderation DMs use a Scrump-coloured embed by default, with the action as the title, the reason, the moderator, and the server name and ID.

Review and revoke moderation

Use /moderation-history target: to open a private, paginated history panel for a member. Only server staff can use it. The panel shows who applied each action, its reason, source, date, duration, and current revocation state. Moderators with the permission required for an action can use its inline Revoke button. Revocation does not erase the original record: Scrump records who revoked it, when it was revoked, and the reason. Where Discord supports reversal, Scrump also removes the active ban or timeout. Notes, warnings, purges, and historical actions remain as audit records and cannot be silently deleted.

Purge messages

All purge commands require Manage Messages, respond privately, and include an audit-log reason. Amount-based commands accept between 1 and 250 messages.

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.
You can also run /settings moderation set-log-channel channel:. Leave channel empty to clear the configured log. Scam-protection alerts use this same moderation log channel. 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 choose a moderation message from a dropdown and customize the DM sent to that target. Messages can be plain text or a Discord embed and support these variables: {user}, {user_mention}, {server}, {server_id}, {action}, {reason}, {duration}, {expires}, {moderator}, and {moderator_mention} The dashboard includes a live Discord preview. /moderation-history is an operational staff panel and cannot be customized. 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. Custom messages stop being sent if the server loses Plus. The saved configuration remains available if the subscription is restored.