Logging

Choose what gets logged and route each category to its own channel.

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, timeouts and honeypot triggers.
  • Roles — role sync, autorole, button roles, panel admin actions, drift reports.

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.

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.
Logging — CloudMod Docs | CloudMod