Moderation

All moderation commands require the moderation feature to be active on your plan. It is on by default during the Basic trial.

Each moderation action is its own top-level slash command — /warn, /kick, /ban — with no group or prefix in front of it. Add-and-remove pairs (/role, /timeout, /temprole) stay one command with two subcommands. The Permission action column is the capability name used by the permission system — that is what actually decides who may run a command, and it is what you grant or deny per role on the dashboard.

/warn · /kick · /ban — member actions#

Voice actions — one command each#

Six unrelated actions rather than one /voice group, so each sits in Discord's picker under its own name and carries its own permission.

/channel — channel actions#

/role · /slowmode — roles and pacing#

/pin · /unpin · /thread — message housekeeping#

/massmod — bulk actions#

/punish — jail, blacklist and other member actions#

Actions Discord has no verb of its own for. Every one opens a case, DMs the member (with your appeal link) and can be reversed later.

/case — the moderation record#

Options every action shares#

These are properties of the moderation system, not of individual commands — so every action supports them, and any action added later gets them automatically.

Context Menu Quick Actions#

Right-click any user in your server — Apps menu — for one-click mod actions:

Duration Format#

Tempban and temprole use a flexible human-readable duration format:

Scheduled punishments (tempban expiry, temprole expiry) are persisted to the database and recovered automatically when the bot restarts.

Every moderation action — yours, the escalation ladder's, and Auto-Moderation's — files one numbered case.

A case is the whole record of an action: who did it, to whom, why, the DM that was sent, the evidence attached, when it expires, whether it was reversed, and every internal note staff added afterwards. Case numbers are per-server and sequential, so “see case #42” means the same thing to everyone on your team.

The log is built to be read at a glance. One header row — Case 2 | Ban | azul.roster beside the member's own avatar — then a single three-column grid: User, Moderator and Reason side by side, and the muted ID: … at the bottom. The left border says which kind of case it is: red for a damaging action, gold for the restore that lifts one (an unban or an un-blacklist), and the general moderation orange for everything else. A temporary action adds its duration and expiry, automation adds where it came from, the DM outcome appears only when it was not routine (a silent action, or DMs that were closed), and evidence rides along — while the category, the channel the command was typed in and the surface it came from are deliberately not on it: they describe the conversation, not the case.

What a case carries#

Appeals#

Every punishment DM carries an Appeal this decision button alongside the member's case number. You set where it goes in Dashboard → Punishments & Cases → Settings, and there are two destinations because a punished member is not always still in your server:

Set either, or both. If you only set the link, it is used everywhere; if you only pick a channel, removed members simply get no button rather than a dead one.

You do not have to leave the page to make that channel: the picker creates one in place (New), and its Create channel button opens the same creator as a dialog with the access panel shown up front — an appeals channel is usually read-only for everyone but staff.

Warnings add up, and a ladder decides what happens at each rung. Fully customisable — or leave it alone and use the built-in one.

The default ladder#

Every server starts here, with nothing to configure. One step is added per warning, and each step is harsher than the last:

The moment you edit it, it becomes your ladder — Azra's future changes to the built-in one stop affecting your server. Order is the whole idea: drag the steps up or down to change what happens next, and every step keeps its own warning count.

The quarantine step needs no setup — if the server has no quarantine role, Azra creates and configures one the first time it is used (see Restriction roles on the Escalation tab).

Building your own#

From Dashboard → Punishments & Cases → Escalation you can create as many ladders as you need, each with unlimited levels, and:

• Different ladders for different categories — a spam ladder that times members out, a toxicity ladder that bans.
• Different ladders for different roles — a stricter one for unverified members, a gentler one for boosters.
• Different ladders for specific channels or whole categories — stricter rules in support channels than in off-topic.
• Drag-and-drop reordering of levels, plus duplicate, import and export so a ladder you like can be reused across servers.
• Priority, for when you deliberately want one ladder to beat another.

When more than one ladder could apply, the most specific wins: a category-matched ladder beats a general one, a role-scoped ladder beats a server-wide one, and your own priority setting breaks any remaining tie.

What a level can do#

Each rung sets a warning threshold and a punishment, and can carry its own DM to the member, its own public notice in the channel, and its own note for staff in the log. Leave a message blank and Azra writes one — naming the action and the reason.

How the counting works#

• A rung fires once. Warning 4 does not re-run the rung at 3 — and a member who jumps from 1 to 4 warnings still gets the rung at 3 rather than skipping it.
• Warnings can expire after a number of days you choose. An expired warning stays in the member's history but stops counting.
• The counter can reset after a configurable quiet period.
• Counters can be per-category, so three spam warnings never push someone over a toxicity ladder.
• Automatic downgrade (off by default) reverses a still-standing escalation punishment once expiries drop the count back below its rung.
• Roles can be exempt from automatic escalation entirely, and escalation can be switched off per category or server-wide.

Who is told what#

Every action Azra takes sends three messages, and each one can be turned off on the Settings tab:

• Staff get a case log in the channel configured for that event — naming the action, the member, the moderator or automation behind it, the reason and the case number. If nothing is configured, or the channel it points at has been deleted, Azra creates the right log channel itself (#moderation-logs, #automod-logs, #security-logs) and records the route, so an action is never invisible. See Moderation Logging.
• The member gets a DM with what was done and why, their case number, the duration and your appeal button — plus what happens next: "If this happens again: Timeout — at 2 warnings", read from the ladder that governs them. Turn it off with DM the member when action is taken.
• The channel where it happened gets a short public notice naming the action and the reason, so the people who saw the behaviour also see it handled. A level with its own public message uses that text instead. Turn it off with Post a public notice when a member is actioned.

Every action is posted to Discord as a rich embed via a webhook styled with your Branding. Mod logging now lives on the central Logging page alongside every other module's logs.

Open Dashboard → Logging, enable logging, and pick a default channel (or a dedicated channel per event). You no longer paste webhook URLs — pick a channel and the bot creates and manages the webhook for you. Moderation events you can route individually:

Events you can route#

One channel per event#

Actions taken outside Azra#

Powered by Discord's built-in AutoMod. When you enable a filter, Azra creates the matching AutoModeration rule in your server — so it keeps working even when Azra is briefly offline, applies to edited messages too, and blocks offending messages the instant they're posted.

What runs where#

Everything Discord's AutoMod can enforce is handled natively; the check it can't do stays inside Azra.

An enterprise-grade layer that sits on top of the native filters above. It adds every protection Discord's AutoMod can't express — anti-raid, anti-nuke, voice/thread/reaction abuse, username & profile scanning, attachment and image checks, and much more — with 182 rules across 23 categories, each individually configurable.

Every rule, individually configurable#

Each rule exposes the same complete control set:

First offence vs repeat offenders#

A punishment answers behaviour, so a rule only reaches for it once the behaviour has shown itself to be a pattern. On a rule's first hit against a member, a simple rule (low or medium severity) warns them — the message is still deleted or blocked, the violation is still logged, and the member gets a DM — and the punishment you configured lands on the third break of that same rule within 7 days. A serious rule (high or critical) — scams, phishing, slurs, threats, anti-nuke, raid — is punished straight away, because waiting for a second scam link is the wrong trade.

How long that punishment lasts is severity's business too: a timeout defaults to 5 minutes on a low-severity rule, 10 on medium, 15 on high and 30 on critical — and every rule's card has its own Timeout duration box when you want a different number.

The rule catalogue#

Rules are grouped into 23 categories. Filters marked Native are pushed onto Discord's own AutoMod where possible (and always run inside Azra too); the rest are enforced by Azra.

Shared settings#

A few settings are shared by every rule that uses them, set once at the top of the page: the Quarantine and Jail roles, the Staff role pinged by Notify staff, an optional alert webhook for the Custom webhook action, and the default DM message.

Uses Discord's native Spam filter, which automatically detects and blocks spammy, repeated and mass-posted content on Discord's side — no thresholds to tune.

Turn it on from Dashboard → Moderation → Anti-Spam — a single switch. When enabled, Azra adds Discord's Spam-content AutoMod rule to your server (it needs the Manage Server permission, same as Auto-Moderation). Blocked spam is recorded to your logs like any other moderation action.

Take action on multiple users at once — ideal for raid cleanup after an attack.

Every target is confirmed before anything runs, and each action is logged individually to your mod log.