Skip to main content
Percy’s audit log watches your server in real time and posts a detailed embed to a channel of your choice whenever a moderation or server event occurs. Every embed includes who performed the action, who or what was targeted, any changes that were made, and the reason provided. This gives your moderation team a single, searchable record of everything that happens on the server. Audit log setup requires the Manage Guild or Manage Messages permission.

​
Setting Up the Audit Log

1

Designate a log channel

Pick — or create — a channel where Percy should post log entries. Restrict it so only moderators can read it, then run:
Percy creates a webhook in that channel and starts posting events immediately.
2

Choose which events to log

By default all supported event categories are active. Use /moderation auditlog alter to turn individual categories on or off:
Pass all as the flag to enable or disable every category at once:
When you run the command, Percy will autocomplete available flag names so you don’t need to memorise them.
3

Set up a separate alerts channel (optional)

Moderation alerts are distinct from the audit log — they surface live AutoMod triggers and raid warnings as they happen. Point Percy at a dedicated channel:
Keeping alerts separate from the audit log makes it easy to triage active incidents without scrolling past historical entries.

​
Events Logged

Percy groups audit log events into named categories. You can toggle each category independently with /moderation auditlog alter.

​
Moderation Alerts

Moderation alerts run alongside the audit log but serve a different purpose: they notify your team about events that need an immediate response, such as a raid or an AutoMod trigger, rather than logging historical changes.
To disable alerts later, run:
You can review the current state of both the audit log and the alerts channel at any time by running /moderation with no subcommand.
The audit log channel should be visible only to your moderation team. Set Discord channel permissions to deny View Channel for @everyone and grant it only to your moderator roles.
Use separate channels for the audit log and moderation alerts. The audit log gives you a complete history; the alerts channel surfaces events that need action right now. Mixing them makes both harder to use.

​
Disabling the Audit Log

If you need to stop logging temporarily, run:
Cases and historical records are retained in Percy’s database — only the channel posting stops. You can re-enable posting at any time with /moderation auditlog set.

​
Next Steps

Server Setup

Set a custom prefix and run through the full initial setup checklist.

Command Permissions

Control which commands Percy responds to per channel and server-wide.