Metryx

Moderation

One shared modlog, actions from the dashboard or straight from Discord, and protection for the bad days.

The modlog

Where to find it:SidebarModerationLogs

The modlog is the single record of every moderation action on the server, whether it came from the dashboard, a slash command in Discord, or AutoMod acting on its own. Every entry is a case: target, moderator, reason, evidence, status.

Filter by action, status, or moderator. Need it elsewhere? Export the whole log as CSV with one click.

Taking action

Warn, timeout, kick, ban, and tempban. You can act from a member's page, from the modlog, or from inside Discord. Every duration field accepts shorthand:

duration shorthand

30m   2h   1d   7d   1d12h

Tip

Timed actions clean up after themselves. When a timeout or tempban expires, it lifts automatically. No follow-up task, no forgotten unban.

Slash commands

The bot ships moderation slash commands so your team never has to leave Discord: /warn, /timeout, /kick, and /ban (add a duration to make it a tempban). Actions taken in Discord land in the same modlog as dashboard actions.

Note

Proof images attached to commands get mirrored to Metryx's own storage, so your evidence outlives Discord's expiring CDN links.

/modlogs posts a member's case history to the channel so the whole team sees the same record, and includes a link to the full history online. That link is a mini dashboard for your Discord staff: the member's cases, the server's full moderation log, and every case detail with proof, reason edits, and the acting moderator — all as clickable rows. Staff without a Metryx account sign in with Discord; access is checked against their current staff roles on every visit.

Warn escalation is configurable under Moderation → Settings: N warns within a window can auto-escalate to a timeout or ban.

Member DMs

When you action a member, the bot DMs them: what happened, the reason, and (if appeals are set up) a link to appeal. The copy is plain language on purpose, and it never leaks rule names or automation internals to the member.

Anti-raid & panic mode

Where to find it:SidebarModerationProtection

Protection covers the emergencies. Anti-raid watches join velocity and reacts on its own when a raid pattern hits. Panic mode is the big red button: one click locks things down while you deal with whatever is happening.

Note

Panic timeouts are pure containment. They don't create cases, so a hundred panic actions won't bury your modlog.

Permissions & the Staff role

Where to find it:SidebarModerationSettings

Two layers here. Dashboard access follows profile roles, managed in the moderation settings. On the Discord side, a dedicated Staff role marks who the bot treats as staff: exempt from AutoMod and allowed to use moderation commands.

Warning

Set the Staff role before turning on aggressive AutoMod rules. Otherwise your own moderators can get caught by their own filters.

Analytics & performance

Where to find it:SidebarModerationPerformance

The Performance page shows the health of moderation itself: action KPIs and trends, a repeat-offender leaderboard, a heatmap of when incidents happen, and per-moderator stats. Who handles what, and how fast.

Want one person's record? The modlog filters to any single moderator.

PreviousInstagram tools NextAutoMod