Lumabot

Moderation and security · Moderation

Logs

A private record of what your moderators and the bot do.

Overview

Logs write what happens on your server in channels only your team can read: who did what, to whom, and why. They watch Discord itself, so an action counts whether it was done with Lumabot's commands or by hand in Discord. They are how you keep moderators accountable and find out what happened while you were away. Each kind of event has its own channel, so the moderation log stays readable.

What goes where

Every entry says who did it, and the reason when there is one. Here is what each log receives.

Moderation log
Sanctions given with Lumabot's commands (bans, tempbans, kicks, timeouts, warnings, blacklist, deranks, nicknames, renewed channels), and bans, unbans and kicks done directly in Discord.
Message log
Deleted and edited messages (with their attachments), messages deleted or pinned by a moderator, and everything the Antilink, Badwords, spam and @everyone filters catch.
Voice log
Members joining, leaving and switching voice channels, muting, deafening, streaming and turning their camera on or off, and moderators disconnecting, moving, muting or deafening someone.
Channel log
Channels, threads and webhooks created, edited and deleted, permission overwrites changed, and the lock, hide, slowmode, clear and delete commands.
Role log
Roles created, edited and deleted, role commands, and temporary and sticky roles.
Invite log
Invites created, edited and deleted.
Urgent log
The serious events: server settings changed, a bot added, and everything the antiraid does (what it caught and the sanction it applied).
Emoji, Ticket, Casino and Giveaway logs
Emoji commands, tickets (closed, claimed, reopened, deleted, and the ratings), the casino and giveaways.

A moderation log entry

Setting it up

/guild log needs the Manage Server permission, and has three pages: the settings, then the channel of each log. You can pick channels you already have.

The quick setup does everything at once: it creates a role, a private category with one channel per log, hidden from everyone except that role, and connects them. Give the role to your team. The access roles setting decides which roles can read the log channels, and changing it updates the permissions of every log channel.

The channels page

/guild log

Opens the log panel. The quick setup button creates the role, the category and the channels after a confirmation.

Need a hand?

Our support server is the fastest way to get help or suggest a feature.