Moderation Commands

Warn, mute, kick, ban and jail members, purge messages, lock channels and read the numbered case record. Every action runs through one executor, so it is cased, logged, DM’d and undoable whichever surface issues it.

Slash Member actions — one command each#

Each action is its own top-level command — /warn, /kick, /ban — with no group or prefix to remember. Each keeps its own permission, so a server delegating junior moderation hands out exactly the actions it means to. Add and remove pairs (/role, /timeout, /temprole) stay one command with two subcommands, so related actions sit together in the picker.

Slash /punish — beyond Discord’s own verbs#

Each is its own permission on purpose: "may kick" and "may permanently blacklist" are different levels of trust, and reviewing an appeal is routinely delegated to staff who may not issue the punishment.

Slash Voice moderation — one command each#

Six unrelated actions, not two halves of one, so each is its own top-level command with no /voice group to remember — exactly like the member actions above. Every one keeps its own permission and its own prefix twin.

Slash /channel — channel state#

Slash /slowmode — rate limit#

The one slowmode command: the old /channel slowmode subcommand was removed rather than kept as a second path to the same action.

Slash /pin & /unpin — message pins#

Slash /thread — create or close a thread#

One command for both directions; `close:true` is an option, not a second command. `message` accepts an ID or a message link, and channel_id disambiguates a bare ID that belongs to another channel. Without `message` the replied-to message is used where Discord supplies it (`!thread` covers text replies); with `close:true` and no message, the thread the command runs in is deleted. A public thread is attached to its source message — Discord cannot attach a private thread to a message, so private:true creates one in the same channel and links the message inside it.

Slash /case — the moderation record#

Reading history is split from changing a case: undoing a punishment and rewriting a stated reason are both audit-sensitive and separately gated.

Slash /massmod — bulk actions#

/massmod stays one grouped command rather than four top-level ones: its bulk actions share a single Mass Mod capability, and keeping them together keeps the command list short. Each action still names its own target, reason and — where relevant — role or duration.

Menu Right-click a member#

User context-menu commands. They share their slash twin’s permission, so a denied capability cannot be reached by right-clicking instead.

Text Text commands#

Shown with the default ! prefix — use your server’s prefix or @mention the bot. Every punishing text command runs through the same executor as its slash twin, so it produces the same case, DM, log and escalation. Flags: --silent, --dm <text>, --note <text>, --for <duration>, --category <name>, --days <n>.

Every other part of Azra that adds commands to your server.

Text commands#

Every text command is shown with the default ! prefix. Your server can change it (!prefix <new>, or the dashboard), and @mentioning the bot always works as a prefix whatever you set — so @Azra help is a reliable way back in if you forget it.

Permissions#

Azra does not read Discord's own permissions to decide who may run what — it has its own Permission Manager, and the server owner and Discord Administrators always hold everything. A capability is an action, not a command path: denying Ban blocks /ban, !ban and the right-click Quick Ban together, so a restriction cannot be dodged by switching surface.

If a command does not appear in Discord#

• Commands register globally and can take a few minutes to show up after the bot joins. Fully restarting your Discord client usually settles it.
• Check the module is switched on for your server, and that your plan covers it — see Plans.
• A command you cannot see may simply not be granted to you. /permissions view shows exactly what a member or role holds.