How to Set Up Moderation Logs in Discord

By default, a lot of what happens in a Discord server is ephemeral: an edited message loses its original text, a deleted message is just gone, and a role change is only visible to whoever happened to be watching Server Settings at the time. When something goes wrong — a dispute, a moderation decision that gets questioned, a compromised account — the first question is almost always 'what actually happened, in order,' and without logging, the honest answer is often 'nobody knows for sure.'

Discord's built-in Audit Log records administrative actions — role and permission changes, channel creation and deletion, ban/kick actions, and similar server-configuration events — for 45 days, visible to members with the right permission. It's a real, always-on record, but it's scoped to admin-level actions and doesn't cover ordinary message activity or give you control over where records live or how long they're kept.

Logging turns the server activity you select into structured, staff-visible records in a channel you choose — designed for operational awareness, not a raw firehose of every internal Discord event.

• Covers channels, pins, roles, threads, emoji, stickers, integrations, and webhooks.
• Covers member joins/leaves, role changes, timeouts, kicks, bans, and unbans.
• Covers message edits, individual deletes, and bulk deletes where Discord provides the required content and context.
• Covers voice activity, invites, and scheduled server events, plus Airwavy's own moderation cases and other configured feature activity.
• A separate Audit Log (Premium) tracks dashboard configuration changes specifically — which setting changed, its before/after value, and who made it — complementing rather than duplicating this feature.

1. Create a private staff channel for logs, visible only to the staff who should see it.
2. Allow Airwavy to view the channel, send messages, embed links, and attach files where required.
3. Open Logging in the dashboard, choose the destination, and enable only the activity groups your staff will actually review.
4. Save, then perform a harmless test — edit a test message or change a test role — and confirm it appears.

• Enabling every available activity group at once — a log channel nobody reads because it's too noisy is worse than a focused one.
• Posting logs to a channel with too broad an audience — message logs can contain member-authored content, so keep the destination to the smallest appropriate staff audience.
• Treating Airwavy's logs as a full replacement for Discord's own Audit Log — they complement each other, and Airwavy doesn't guarantee content Discord didn't make available to it.
• Never revisiting the configuration — review and remove obsolete log destinations when staff roles or channel access change.