As a server owner or administrator, you need to track changes made by members and bots to maintain security and order. The Discord Audit Log records every significant action performed in your server, from role edits to channel deletions. Many users find the log overwhelming because it displays all entries in chronological order without clear organization. This article explains how to open the audit log, interpret each entry, and use filters to find specific events quickly. By the end, you will be able to monitor your server effectively using the built-in logging tools.
Key Takeaways: Reading and Filtering the Discord Server Audit Log
- Server Settings > Audit Log: The central location where all server actions are recorded and displayed.
- Filter by Action Type: Use the dropdown menu to narrow logs to specific categories like Role Changes, Channel Updates, or Member Bans.
- Filter by User: Select a specific member or bot to see only actions performed by that account.
What the Discord Server Audit Log Records
The Audit Log is a built-in feature available to server members with the View Audit Log permission. By default, server administrators and members with the Manage Server permission can access it. The log records actions such as creating or deleting channels, changing role permissions, updating server settings, kicking or banning members, and moving voice channels. Each entry includes the action performed, the user who performed it, the target object, and a timestamp. The log retains entries for up to 90 days, after which older entries are automatically removed.
The log does not record every minor action. For example, editing a message or reacting to a message does not appear in the audit log. Only actions that change server structure or permissions are logged. Bots that have the necessary permissions also appear in the log when they perform actions.
Who Can Access the Audit Log
To view the audit log, a user must have the View Audit Log permission enabled in their role. Server owners automatically have this permission. Members with the Administrator permission also inherit access. If you cannot see the audit log, ask a server admin to grant your role the View Audit Log permission in Server Settings > Roles > [Your Role] > Permissions.
Steps to Open and Filter the Audit Log
Follow these steps to access the audit log and filter entries by action type or user.
- Open Server Settings
Click your server name at the top-left of the Discord window. From the dropdown menu, select Server Settings. This opens the server configuration panel. - Navigate to Audit Log
In the left sidebar, scroll down and click Audit Log. The main pane displays all recent actions in reverse chronological order, with the newest entries at the top. - Filter by Action Type
Click the dropdown menu labeled All Actions at the top of the log. A list of action categories appears, such as Channel Create, Channel Delete, Role Create, Role Update, Member Update, and more. Select a specific action to show only entries of that type. - Filter by User
Click the dropdown menu labeled All Users next to the action filter. Type a username or select a user from the list. The log updates to show only actions performed by that user. - Combine Filters
You can apply both filters simultaneously. For example, select Role Update from the action dropdown and a specific user from the user dropdown. The log then shows only role updates made by that user. - View Details of an Entry
Click any entry in the log to expand it. The expanded view shows the exact changes made, such as the old and new values for a permission update or the name of a deleted channel.
If the Audit Log Is Not Showing Expected Entries
Sometimes the audit log may appear empty or missing entries you expect to see. This section covers common reasons and how to resolve them.
Audit Log Shows No Entries at All
If the audit log is completely blank, the most likely cause is that your role lacks the View Audit Log permission. Ask a server administrator to grant this permission. Another possibility is that your server is very new and no actions have been performed yet. Perform a test action, such as creating a text channel, and check if it appears in the log.
Specific Actions Are Missing
Not all actions are recorded. Message edits, message deletions, and message reactions are not logged. Only actions that modify server structure, permissions, or member status appear. If you expected a message-related action to appear, you need to use a moderation bot with message logging features instead.
Entries Older Than 90 Days Are Missing
Discord automatically removes audit log entries older than 90 days. There is no way to recover or export the audit log natively. To keep a permanent record, consider using a bot that logs actions to a separate channel or an external service.
Discord Audit Log vs Moderation Bot Logging
| Item | Discord Audit Log | Moderation Bot Logging |
|---|---|---|
| Access | Built-in, requires View Audit Log permission | Requires bot setup and dedicated channel |
| Retention | 90 days maximum | Unlimited if bot stores data externally |
| Actions recorded | Server structure, permissions, member actions | Can include message edits, deletions, joins, leaves |
| Filtering | By action type and user | Often by date, user, action type, and keyword |
| Export | Not supported natively | Many bots offer export to CSV or JSON |
You can now open the audit log, apply filters to find specific changes, and understand what each entry means. For long-term record keeping, consider adding a moderation bot that logs message edits and deletions to a private channel. A useful tip is to assign the View Audit Log permission only to trusted moderators to prevent unauthorized users from seeing sensitive changes. Regularly reviewing the audit log helps you catch unauthorized modifications early and maintain server order.