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 records member, role, server and moderation events regardless of these toggles. Voice, bot-action, raid-alert, ticket and message logs only go to Discord.

Categories

Categories are grouped:

• Members — joined (with account age, member number and, with Invite Tracking, who invited them), left, kicked (with the responsible moderator), nickname, roles, username and avatar changes.
• Messages — edited, deleted and bulk-deleted, including the old content.
• Server structure — 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, plus /warn, /note and /purge.
• 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.
• Support — Ticket Bot events: tickets opened, claimed, unclaimed, transferred, closed or reopened.
• Bot logs — audit-log actions performed by members of a bot role you choose (see below).

Two kinds of entry are always posted, whatever you switch off: ⛔ Role can't be assigned (once per role per day) and ❌ Error entries. If you set an admin role under Project settings → Admins & permissions, CloudMod pings it for these — at most once an hour, and only if the role is mentionable.

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.

Role-change log cooldown

Some bots add and remove a role within seconds (for example a reward role tied to a custom status), which floods the Member roles changed log. The Role-change log cooldown card on the Logging page limits each role change per member to one post in the window you pick (Off, or 1 hour up to 7 days). It only throttles the Discord posts — the dashboard Audit Log still records every change.

Per-category channels

Each category can target its own channel, or fall back to the project's default log channel (set in Project settings → General → 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 in your main server with a curated set of channels (mod-logs, scam-guard, honeypot, account-age, raid-alerts, ticket-logs, member-logs, role-logs, message-edits, message-deletes, channel-logs, server-structure, invite-logs, voice-logs, bot-logs — each name gets an emoji prefix, e.g. 🛡️・mod-logs) and routes every logging category to its matching channel. Only CloudMod and your admin role can see them. It's idempotent — channels with the same name are reused, never duplicated — and you can fine-tune the routing afterwards.

When CloudMod can't post in a log channel

If a log entry can't be delivered, because CloudMod is missing a permission in that channel or the channel was deleted, the dashboard tells you:

• the alerts bell shows how many log channels are affected,
• the Logging page names each channel, what's missing and which categories use it.

Give CloudMod's role View Channels, Send Messages and Embed Links in the channel (check the channel's and its category's permission overrides), or pick another channel. Then hit Check again. The alert also clears on its own as soon as the next log entry gets through.

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.
• Avatar changes show the old picture at the top left and the new one on the right. CloudMod saves a small copy of the old picture the moment the change happens and attaches it to the log message — Discord often deletes old avatars right away, so a link alone would show nothing. This needs Attach Files in the log channel; without it the entry still arrives, just without the old picture, and says why. If Discord no longer had the old picture at all, the entry says so. The picture is only posted in your log channel, never stored by CloudMod.

What a log entry looks like

Every entry follows the same layout:

• Top line — the member's name and avatar, when a member is involved (message logs show the author's name only).
• Title — what happened, with an icon.
• One sentence — who did what, and where. Names are clickable. A deleted-message entry shows the deleted text here instead.
• Footer — the server it happened on (with its icon, where available) and the member's ID. In a network all servers can share one log channel, so the footer tells you which one.

Colors mean the same thing everywhere:

Color	Meaning
Green	something was added
Red	something was removed, or a member was punished
Dark red	the severest cases — bans, Honeypot and Scam Guard hits, and errors
Orange	CloudMod needs you — e.g. a role it can't assign, an action that failed, a raid alert
Blue	something changed
Grey	just for your information

Every entry is its own card with all its details, even when several arrive at the same moment — CloudMod then sends them together in one message, in the order they happened.