All 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>.

XP for messages, voice, reactions and threads, with rank cards, level roles, prestige and a server leaderboard. Members serve themselves; only the XP admin tools are gated.

Slash For members#

Self-service commands. These bypass the permission system entirely and can never be denied.

Slash For admins#

Text Text commands#

Scheduled multi-winner giveaways with eligibility rules, bonus entries and prize-claim tickets. Members enter from the buttons on the giveaway message — the commands are the manager surface.

Slash Managing giveaways#

Managers are members with Manage Server or a configured giveaway manager role. The id every lifecycle command takes is the giveaway’s message ID — right-click the message → Copy Message ID.

Text Text commands#

The same lifecycle controls. Creating a giveaway needs a modal, which a text message cannot open — use /giveaway create or the dashboard. Aliases: !gw, !ga

Buttons On the giveaway message#

Members never need a command — everything available to them is a button on the giveaway itself.

A full support platform — departments, intake forms, SLA clocks, routing and transcripts. Members open tickets from a panel and work entirely from buttons; /ticket is the staff keyboard surface.

Slash /ticket — the staff surface#

Run inside a ticket channel, except /ticket staff. Not one subcommand writes a ticket itself — they all call the same executor the buttons and the dashboard do, so SLA clocks, the event history, metrics, webhooks and automation triggers all apply. Closing is deliberately not gated: the member who opened a ticket may close it, until somebody else replies.

Buttons In the ticket channel#

The rest of the platform is driven by buttons, so members need no commands at all.

Multi-step Discord forms with conditional questions and a reviewable response queue — applications, feedback, bug reports and signups, with or without a support ticket behind them.

Text Text commands#

!form open does not exist and cannot: starting a form means showing a modal, and Discord only allows one in reply to an interaction — a text message is not one. The one /form slash command was removed; authoring and responses live on the dashboard, members answer from a panel button. Alias: !forms

Self-assignable role panels as reactions, buttons or a dropdown. The dashboard builder is the richer surface — these commands cover the whole lifecycle from Discord.

Slash /reactionroles#

A message that reposts itself at the bottom of a channel whenever conversation scrolls past it.

Slash /sticky#

Mention every new member in a channel, then delete the ping about a second later — it draws them in without leaving clutter. Deferred until captcha is passed when a verification gate is on.

Slash /ghostping#

Text Text commands#

Alias: !gp

Join and leave messages as an embed, a designed image or plain text, with auto-roles, DMs and link buttons. The message itself is built in the dashboard designer — these commands are the quick switches.

Slash /welcome#

Twitch go-live and YouTube upload notifications. Adding and removing integrations is done entirely from the dashboard; the one command lists what is configured.

Slash /socials#

Snapshots of your channel and role structure, and a non-destructive restore that recreates whatever is missing.

Slash /snapshot#

A summary of server activity and moderation in Discord. The full 30-day dashboard, heatmaps and per-user lookup live on the web.

Slash /stats#

Text Text commands#

The Permission Manager, in Discord. It writes the same grant tables the dashboard page does, through the same guards — a grant made here is the grant there.

Slash /permissions#

target is one mentionable option — pass a user or a role and the subject type is read off whichever you picked. permission is autocompleted and covers modules (module:moderation) and single capabilities (cap:slash:ban) in one vocabulary. Gated by the very capability it hands out: the server owner and Discord Administrators always hold it.

Always available, never gated, and unaffected by your plan.

Slash Slash commands#

Text Text commands#

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.