Lona Docs DOCS
Ctrl K
Dashboard Support Add Lona
Docs / Audit logs

Audit Logs

Comprehensive logging for messages, member events, and moderation actions.

2 recipes
How to configure it from the dashboard

Audit logs work smartly: they automatically create threads inside a single channel for each log type—instead of creating 40 channels. Everything stays organized in one place.

Select the log channel

Dashboard ← Audit logs

Choose a single channel, and Lona automatically creates a thread in it for each event type.

Hide it from regular members—the log channel is a goldmine of information for raiders.

Audit logs
Log channelLona creates threads inside it#📋│audit-logs
Enable allDisable all

Start with essential categories only

Audit logs ← Categories

Don't click "Enable all" on a large server—you'll drown in data and won't read a single line.

Start with these: Punishments (ban / timeout / warn), role changes, and message deletions. These are what you actually need during investigations.

Categories — Security and punishments
🚫 BanModerator + reason from Audit Log
🔓 Unban
🤐 Timeout / remove timeoutDuration + moderator + reason
⚠️ Warn
🏷️ Nickname or role changeRoles added/removed + who changed them
🗑️ Message deletionContent + attachments + stickers + deleted by
Over 40 event types available—enable only what you need

Understand what each type logs

Audit logs ← Details under each option

Lona doesn't just log "something happened"—it records the details you actually need:

Member join — Account age + which invite was used + alert for new accounts
Leave / kick — Distinguishes voluntary leave from kicks + stay duration
Message edit — Text before and after + message link
Avatar or username change — Global avatar, server avatar, and username

Role changes and avatar/username changes are more important than you think: the former reveals compromised mod accounts, and the latter catches impersonators attempting scams.
📥 Member joinAccount age + invite used
📤 Leave / KickDistinguishes voluntary leaves from kicks + stay duration
🖼️ Avatar or username changeCatches moderator impersonators
✏️ Message editText before and after + link

How the system works

The comprehensive log is your server's black box. Lona logs over 40 event types grouped into categories:

Messages — Delete, edit, bulk delete
Members — Join, leave, kick, nickname change, role change, boost, verification
Accounts — Avatar or username change
Punishments — Ban, unban, timeout, remove timeout, warn
Voice — Join, leave, move, mod action, activity, stage
Channels & threads — Create, delete, edit, permission changes
Roles — Create, delete, edit
Server — Settings update, emoji, stickers, invites, reactions

The game-changer: you can split each category into its own channel instead of dumping everything into one unreadable channel. Lona even names the channels clearly for you, like 🗑️-حذف-رسالة and 🟢-دخول-صوتي.

And !modlog sets the dedicated mod action log channel — separate from general event logs.

Practical recipes

Set up a log you will actually read

The problem isn't logging, it's making sure someone actually reads it:
1Dashboard ← Comprehensive Log
2Split categories: one channel for messages, one for members, one for punishments
3!modlog #channel — for mod actions log
4Hide log channels from regular members

Investigating an incident

The fastest order to uncover the truth:
1!history @member — their punishment history
2!snipe or !editsnipe — if the issue was a deleted message
3!من_دعاني @member — if the account is suspicious
4Check the role log channel if permissions were escalated
Tips and warnings
The role change log is more critical than you think — the first sign of a compromised moderator account is granting roles to new accounts.
The avatar and username change log exposes users impersonating staff to scam.
Don't enable all categories at once on a large server — start with the essentials (punishments, roles, message deletions) and scale up gradually.
Logging only records from the moment of activation onwards — it cannot retrieve the past. Enable it before you need it.
Log channels must be hidden from members, or they become an intel source for raiders.