Server Assistant📜 The audit log
Every time a moderator acts in your server, Server Assistant writes it down. That record — your audit trail — is how you answer the questions that come up after the fact: who removed that member, when the channel was locked, why someone was banned. It runs on every plan, with nothing to switch on.
FREE The audit log is part of every plan.
There are two halves to it, working together:
- A visible log channel in your own server (you choose it during
/setup), where each action lands as a tidy embed your whole team can read. - A separate, encrypted record kept off to one side that staff cannot read, edit, or erase — so even if someone tidies up the visible channel, the real history is still there.
In short: the log channel is the window your team looks through; the encrypted record is the safe behind the glass. You can break the window — you can’t open the safe.
What gets logged
Server Assistant records the things that actually matter for accountability:
- Moderation actions — warnings, notes, mutes, kicks, bans, soft-bans, temp-bans, locks, lockdowns and the rest. Each one is logged with who did it, what they did, to whom, and the reason they gave.
- Actions taken directly in Discord — if a moderator bans or kicks someone using Discord’s own menus (not a Server Assistant command), the bot notices and logs it for you anyway, clearly marked as a native action.
- Command usage — a compact, one-line entry each time a command is run, so you can see who’s been driving the bot even when a command doesn’t change anything.
A moderation action in the log
When a command like /ban runs, the action lands in your log channel as a full
embed — the same one the command author sees, mirrored to the team:
An action taken directly in Discord
Moderate with Discord’s built-in tools and Server Assistant still keeps your trail complete. It mirrors the action into the log channel, marked so you can tell it apart at a glance — with a friendly nudge towards doing it through the bot next time (which keeps the one-tap undo):
Native bans, unbans, kicks, timeouts, role changes and channel deletions are all picked up this way.
A command-usage entry
Every command leaves a light footprint too — a single grey line naming who ran what, and where. Commands that already produce a detailed entry (like the ban above) are skipped, so you never see the same thing twice:
You can turn these compact command-usage lines on or off in /settings →
Behaviour — the detailed moderation entries above always log regardless.
Why it’s tamper-proof
The whole point of an audit trail is that it stays trustworthy even when someone would rather it didn’t. Server Assistant is built so the record can’t be quietly wiped:
- A separate, encrypted record. Alongside the visible channel, the bot keeps its own encrypted log of every moderation action. It lives outside Discord, and staff cannot read, edit or erase it — there’s no command, button or permission that lets a moderator reach in and change history.
- Deleting log messages doesn’t delete the truth. Someone can delete a message from the visible log channel — but doing so changes only the window, not the safe. The underlying encrypted record is untouched.
- And you’ll know if they try. If a message is deleted from your log channel, Server Assistant spots it and raises an alert — to your log channel and to the server owner — naming who did it:
If the log channel itself is deleted, the bot simply notices it’s gone and clears the setting so you can pick a fresh one — and, again, the encrypted record carries on untouched the whole time.
Setting your log channel
Your log channel is chosen during the /setup wizard, on the Channels
step. The bot detects a likely candidate (often #mod-log) and fills it in for
you — accept it, pick a different channel from the dropdown, or have the bot
🆕 Create for me a fresh, locked-down one that only it can write to.
Want to change it later? Re-run /setup any time — it loads your current
configuration, so you can swap the log channel without starting over. For the
finer controls — how chatty the log is, and whether those compact command-usage
lines appear — open /settings and look under Behaviour.
See also
- The
/setupwizard — choose your log channel and staff roles in about a minute - Moderation & safety — every command that writes to your audit trail