How to Set Up Discord Log Channels and Warning System

Modules, channel permissions and command permissions

• Two modules must be enabled. If the Module status toggle at the top of the Audit Logs tab is disabled, no logs—including moderation logs—will be sent. The Moderation module must also be enabled for /warn and other punishment commands.
• The bot must have permission to write to log channels. In every log channel, the bot must have the permission to view the channel, send messages, and embed links.
• Log channels must be hidden from staff. Message logs show the content of deleted messages. Turn off @everyone's permission to view these channels.
• Permissions must be distributed correctly. You need Manage Server for /setlog; Manage Messages for /warn, /warnings, /note, and /reason; and permission to timeout members for /case-history.

This topic in VeyroBot:Discord Moderation Bot →

Step 1: Determine the channel layout

There are six log types, and each goes only to its own channel. A type with no channel selected is disabled.

Two channels are enough for a small server: one for moderation, one for everything else; the same channel can be selected for multiple types. As the team grows, separating message logs prevents moderation records from getting lost in the noise.

Step 2: Select log channels

1. Open the Dashboard → your server → Audit Logs tab; check that the Module status toggle is on.
2. Select a channel for each type you will use. Only text channels appear in the list.
3. In the Ignored in Message Logs section, add noisy channels like bot command channels and staff roles.
4. Click Save Log Channels.

The command is enough to select only the moderation channel: /setlog channel:#mod-log. If you run it without specifying a channel, the moderation log turns off. The other five types are selected exclusively from the dashboard.

Step 3: Issuing a warning

/warn target:@member reason:reason warns a member. Use the /warn command. Three things happen with every warning:

• The warning is added to the member's counter, and the response shows the total warning count.
• A numbered case is opened and sent to the moderation log channel.
• If the counter reaches a tier threshold, an automatic punishment is applied.

Rules: you cannot warn yourself or bots; unless you are the server owner, you cannot warn a member who has a role equal to or higher than your highest role. No direct message is sent to the warned member. If the member needs to know the reason, message them separately.

The same action is performed in the dashboard under the Web Moderation tab using the user ID: select Warn as the action. Warnings given from the dashboard are also written to the same counter and tier.

Setting up warning tiers

Tiers are located in the Advanced AutoMod → Gradual Punishment System section. Two thresholds and an action for each are selected: warning only, 1 hour or 1 day mute, kick, or ban. Default: 1-hour mute at 3 warnings, kick at 5 warnings.

• Manually given warnings and AutoMod violations are written to the same counter. Even if the AutoMod module is disabled, manual warnings trigger tiers.
• Each threshold is applied to a member once; punishments are not repeated as the counter goes above the threshold.
• /warnings target:@member clear:True or Clear Warnings in Web Moderation resets the tier record along with the counter. If a cleared member reaches the threshold again, the tier is applied once more.

Threshold selection, how they work together with filter punishments, and the impact of false positives are detailed in the AutoMod setup guide.

Checking history: which tool when?

If logs do not arrive or show up empty

• Leaving the module disabled and selecting channels. Channels appear saved, but no logs go through. Check the Module status toggle first.
• The bot not being able to write to the log channel. No error message appears if logs cannot be sent. The Health card in the dashboard's Overview shows log channels that the bot cannot write to or that have been deleted.
• Expecting the content of an old deleted message. Discord does not send the text of deleted messages to bots; the bot can only display content from its own cache. If a message written before the bot started is deleted, the log falls without content.
• Not knowing the consequence of clearing warnings. Clearing also resets the tier record; if you clear the warnings of a member who was kicked and returned, tiers will apply from the beginning.

Does a small server need six log channels?

Suitable for: servers with multiple moderators, where decisions might be questioned later and rules need to be enforced gradually. If your rules are not written yet, check the server rules guide first.

Not suitable for: servers managed by a single person, consisting of a few friends. There, six log channels are nothing more than noise; a moderation channel alone is enough.

Frequently asked questions

Do warnings delete themselves after a certain time?

No. Warnings stay in the counter until you clear them.

What happens if a tier punishment cannot be applied?

If the bot cannot mute or kick the member—for example, if the member's role is above the bot's—the tier is still recorded and the log channel states that the action could not be applied.

Are warnings recorded if I turn off the moderation log channel?

Yes. The warning counter and case record are kept independently of the log channel; only the log message is not sent.

I don't want to see staff messages in the message log. Add staff roles to the role list in the Ignored in Message Logs section. This only affects message logs; staff moderation actions are still recorded.

For a general introduction to the feature, check the Discord moderation bot page; for all settings, check the audit logs and moderation docs; for command details, check the setlog, warn, and vaka-gecmisi cards.

Last updated: September 17, 2026. Log types, warning rules, and tier behaviors in this article have been verified against the log dispatcher, warning commands, and gradual punishment engine in VeyroBot's current version.