docs

Search docs

Search the Metryx documentation

Get started

Moderation

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.

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.

Access keys

Where to find it:SidebarDiscordUtilitiesAccess keys

An access key is a password members redeem to unlock roles. Creating one is a single form: name the key, set or generate the key value, and name a password channel. On save, Metryx builds everything in Discord for you. It makes a public channel where members type the key, grants the roles you picked, and can build an optional private category plus any locked channels you list.

Important

Metryx only accepts roles from the connected server, and it always blocks managed roles. You can grant a role that carries administrator or moderation permissions, but the editor warns you first: anyone who redeems the key gets that role and its power, and if the key or its website link leaks, whoever has it gains that power. You read the warning, wait a few seconds, then check a box to accept the risk before you can save. Metryx is not responsible for leaked keys or links. When you can, use a dedicated access role with no dangerous permissions and let Metryx lock the private channels to it.

Note

Save the access key first, then re-open it. The edit view shows the key's own website link to copy and lets you post a verification button into a channel.

The website link is useful for launches, drops, or off-Discord campaigns where members prove their Discord account before access is applied.

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.