Moderation Ledger and Auditing
The moderation ledger preserves context such as action, target, moderator, reason and time. Use it to understand a decision, not merely count actions.
Read a record
Section titled “Read a record”Open the selected server’s Moderation dashboard area or mod logs for a member. Check target identity, reason and recorded result. Empty history is not permission to fabricate a clean status when storage is unavailable.
Notification is separate
Section titled “Notification is separate”Fork may attempt a target DM after recording/applying an action. DM failure does not prove the moderation action failed. A Discord write can also succeed while later recording or confirmation is uncertain. Inspect actual state and receipts before repeating.
Staff records
Section titled “Staff records”Staff strikes are disciplinary records, not automatic role removals. At three or more, the response recommends evaluation. Clearing strikes records a different decision; zero cleared is explicitly no change.
Dashboard audit logs concern administrative events and are not interchangeable with the moderation ledger or Discord’s own audit log. For support, provide only the relevant redacted record and time, never full unfiltered operational logs.