Skip to main content
Almost all of Lucie’s configuration lives in the web panel, not in commands. You sign in with your Discord account, pick a server and change whatever you want from your browser.
1

Sign in with Discord

Click Sign in with Discord at lucie.elxy.dev. Lucie only asks to read your list of servers; she never acts on your behalf.
2

Pick your server

You’ll only see the servers where you have the Manage Server permission. If a server doesn’t show up, it’s because you don’t have that permission there (or Lucie isn’t in it yet).
3

Configure

Each module saves on its own and applies instantly: there’s nothing to restart and no need to re-invite the bot.
The dashboard uses custom-built controls, not the browser defaults: dropdowns match the site’s look (and open as a thumb-friendly bottom sheet on mobile), and the roles and channels in lists —exemptions, whitelist— are pills you tap to toggle on and off. Lists that grow over time —recent joins, giveaways, audit log, global bans— are paginated 10 at a time, so no page ever becomes endless. The whole dashboard is built to work just as well on your phone as on desktop.

​
Home and Live activity

These are the two fixed entries at the very top of the sidebar.

Home

Server overview with one card per module and its counters. The shortcut for seeing at a glance what you have enabled.

Live activity

Real-time security feed: what Lucie is detecting, global bans, and the manual raid mode and lockdown controls.

​
Main

​
Security

Every protection gets its own page, with its state (enabled or disabled) always visible in the header.
If Lucie detects something while you’re on another panel page, you get an instant notification and a red dot on Live activity.

​
Moderation

The Permissions section is what keeps moderation from depending on Discord’s native permissions: you can authorize a specific moderation role and mark immune roles, without handing out Discord permissions to anyone.

​
The server log, in detail

Lucie posts what a moderator needs to reconstruct what happened. It is split into four categories you can enable separately: Almost everything shows who did it, read from Discord’s audit log, plus the reason when there is one. All of this can be configured by command too, with !bitacora: they’re the same settings, so it doesn’t matter where you change them from.
If you’d rather not fill the server with channels, turn on One thread per category: Lucie opens a thread inside the log channel for each one (she needs permission to create public threads there). And if you prefer real channels, you can give each category its own, which always wins over the thread. Anything left without either falls back to the general channel, so if you only set that one, everything keeps arriving together as before.

​
Purge transcripts

A purge wipes dozens of messages at once, and the embed can only tell you how many and whose. Turn on Purge transcript and Lucie also attaches a .txt with everything that was deleted.
  • A header with the server, the channel, who ran it and the date.
  • A per-author summary: how many messages each one posted, and which are bots.
  • Every message numbered, with time, full content, attachments, stickers and embeds.
  • Replies are resolved within the purge itself, so you can follow the conversation.
  • Each person appears as display name, @username and ID, because the first two change in one click and the ID doesn’t.
It’s a .txt on purpose: Discord previews it inside the client, so it reads without downloading anything, on your phone too. Images and videos are re-uploaded alongside the .txt, so they’re actually kept: Discord CDN links expire shortly after the message is deleted and are no good as an archive. Each file arrives renamed with the number of the message it belonged to (012_screenshot.png), so you can tell where it came from. Discord allows 10 files per message and caps the total size by the server’s boost level, so if a purge brings more than fit, Lucie uploads the ones that do and notes in the .txt which were left out, with their link in case it still works.
It only works with Lucie’s own !purge. On other bots’ purges Discord doesn’t send the message content —only the IDs— so the file would come out incomplete without saying so: there you get the usual notice instead. Keep in mind the file stays in the channel too, so it is the most complete trace Lucie keeps of a deleted message. That’s why it ships off.

​
Sensitive permission warnings

When a change grants permissions that carry real power — Administrator, Manage Server, Manage Roles, Ban Members, Manage Webhooks… — the message turns red and says so in the title. Same when someone disables an AutoMod rule. A colour or name change, by contrast, stays amber with no alarm.

​
Bursts

If someone gives a role to many people at once, you don’t get hundreds of messages: Lucie groups them into one (“47 members received @Verified”). And if it still saturates, it tells you how many entries were skipped instead of swallowing them silently.

​
What it deliberately skips

Avatar, username and display name changes do not go to the log: that is what !avatars and !names are for, showing them when you look. Neither does online status, nor joining and leaving voice channels. The point is to keep the channel readable.

​
Social alerts

One section per platform. You follow an account and Lucie posts an alert in the channel you choose whenever it publishes something new, with a customizable message and a role to ping. It can also be managed by command with !social.

​
What stays in commands

Some things aren’t in the panel because they only make sense in the moment: one-off sanctions (!warn, !ban…), channel cleanup (!purge), snipes and day-to-day music. The panel is for configuration; commands are for action.
Can’t find a setting? Ask in the support server; if it’s missing, it gets added.