Logging

The Logging page lets you decide exactly what the bot posts to Discord — and, per category, which channel it goes to. It's similar to CarlBot's logging: many toggleable categories, each with an optional dedicated channel.

The dashboard Audit Log is unaffected — it always records everything, regardless of these toggles.

Categories

Categories are grouped:

• Members — joined, left, kicked (with the responsible moderator), nickname, roles, username and avatar changes.
• Messages — edited, deleted and bulk-deleted, including the old content.
• Server — channels and roles created/deleted/updated, server settings, emojis/stickers, invites.
• Voice — joined / left / moved / server mute-deafen (off by default — these can be noisy).
• Moderation — word-filter hits, bans, unbans and timeouts.
• Automod — the automatic anti-raid/spam modules, each with its own channel: Scam Guard, Honeypot, the Account age gate and Raid alerts (join-rate spikes).
• Roles — role sync, autorole, button roles, panel admin actions, drift reports.
• Bot logs — audit-log actions performed by members of a bot role you choose (see below).

Bot logs

Want a single feed of everything the bots on your server do? On the Logging page, pick a bot role under Bot logs, then assign that role to the bots (or bot-like accounts) you want to track. From then on, every audit-log action performed by a member of that role — channel edits, role changes, kicks, bans, message purges — is posted to the Bot actions category. Leave the picker on No bot role to keep bot logs off. The role lives on your main server.

Per-category channels

Each category can target its own channel, or fall back to the project's default log channel (set in Settings → log channel). So you can send message logs to #message-log, mod actions to #mod-log, and leave everything else on the default — or just put everything in one channel.

Auto-create channels

Don't want to wire everything by hand? Hit Auto-create channels on the Logging page. The bot creates a staff-only CloudMod Logs category with a curated set of channels (mod-logs, scam-guard, honeypot, account-age, raid-alerts, member-logs, role-logs, message-edits, message-deletes, channel-logs, server-structure, invite-logs, voice-logs, bot-logs) and routes every logging category to its matching channel. It's idempotent — channels with the same name are reused, never duplicated — and you can fine-tune the routing afterwards.

Notes

• Message content is only ever shown in your log channel — it is never stored in CloudMod's database. It's held briefly in memory to recover the old text of an edited/deleted message.
• Moderator attribution (“by X”) is read from the Discord audit log; the bot already has the View Audit Log permission.
• A server that belongs to several projects will log once per project.