Logging

Mirrors Discord events + Phantom actions into a configured Discord channel. Your tamper-resistant paper trail.

What gets logged

Default categories (toggle each independently):

• Moderation actions — every /pmod command + automod hit + warning escalation.
• Member joins / leaves — with account age + invite attribution.
• Member updates — nickname changes, role changes.
• Role changes — server-wide role creates / deletes / permission changes.
• Channel changes — channel creates / deletes / renames / permission overwrites.
• Voice events — VC joins / leaves / mutes (configurable verbosity).
• Message deletes — content + author + channel (the "snipe" log).
• Message edits — before/after content.
• Server settings — verification level changes, AFK channel, etc.
• Emoji + sticker changes — adds, deletes, renames.
• Webhook + integration changes — pairs with Perm Watch.
• Soundboard changes — new sounds, removed sounds.

Where it lives

Dashboard: General → Logging.

Setup

1. Pick a log channel (or multiple — you can route different categories to different channels).
2. Toggle the categories you want.
3. Save.

Events start flowing within seconds.

Multi-channel routing

Useful for big servers: send mod-actions to #mod-log, voice events to #voice-log, message edits to #edit-log, etc. Each category has its own channel field.

Permissions

• guild.view — see settings
• guild.edit — change channel routing + toggles

Tips

• Always log moderation actions. Even small servers — it's your audit trail.
• Voice logs are noisy. Consider only logging VC events on a smaller scoped channel.
• Message-edit logs can leak private content if the channel is widely visible. Restrict access to the edit-log channel to staff only.

Distinct from Security → Audit Log

• Logging (this page) = Discord-side events mirrored as a paper trail. High-volume; for day-to-day mod review.
• Audit Log = Phantom security-system events (raids, scans, fixes). Lower-volume; for incident review.

Both are useful. Most servers run both, in different channels.

Behaviour

• Logs post via the bot — uses your Custom Branding identity if set.
• Per-channel sends are coalesced; a burst of 20 voice events in one second batch into one log message.
• A log-send failure (permission revoked) logs to Error Log for diagnosis.

Related pages

• Audit Log
• Error Log
• Perm Watch