/alerts

Requires: Manage Server

/alerts controls which of Guild Ledger's 42 audit events fire alerts and where they are sent. Events are grouped into 8 categories: members, roles, channels, messages, moderation, server, voice, and integrations.

What you can do

  • Set alert channel โ€” choose where all alerts are posted by default
  • Enable/disable events โ€” toggle individual events or entire categories at once
  • Exclude roles โ€” suppress alerts triggered by members with specific roles (useful for other bots or trusted staff)
  • Per-event routing ๐Ÿ”’ โ€” send different event types to different channels, e.g. message deletions to #message-log and bans to #mod-log

Covered events

Member joins and leaves, role changes, channel edits, message deletes and edits, bans, kicks, timeouts, voice state changes, integration changes, and more โ€” 42 events in total across the 8 categories.

Alerts and audit logging are related but separate: the /config event-logging setting controls what is written to the log, while /alerts controls what is announced in a channel. An event can be logged without alerting, or both.

๐Ÿ”’ = Pro feature