Skip to main content

📋 Mod Log

The Mod Log gives your team a paper trail: bans, kicks, warnings, filter hits, member changes, and more — routed to a log channel, to admin DMs, or filtered out entirely. Every event type has its own toggle and destination, so busy servers can split noisy events from critical ones.

Overview​

  • One default destination, with per-event overrides for channel or DM delivery
  • 26 event types across four categories: Moderation, User Updates, AutoMod, and Gamification
  • Toggles to include or exclude the agent's own actions and manual (Discord-native) actions
  • Native Discord moderation is attributed to the acting admin via audit-log lookups

Configuration​

To configure the mod log:

  1. Open your project in the Fren One webapp.
  2. Select the Discord server you want to configure.
  3. In the sidebar under Agent Configuration, select Moderation, then the Mod Log tab.
  4. Toggle "Log moderation actions to admins" on.

Default routing​

"Where events are routed by default" sets the fallback destination for every event that doesn't override it:

OptionDescription
Default destinationChannel (reveals a required Default log channel picker), Direct message to admins, or Don't log by default. Default: Don't log by default.
Admin roles for DMsMembers with these roles receive log DMs.
"Don't log by default" silences inherited events

With Don't log by default selected, every event whose destination is set to Default won't be delivered anywhere — the page shows a note reminding you. Set a channel or DM default, or give important events their own destination.

Filter the events that are captured​

ToggleDescription
Include Bot ActionsLog actions taken by the agent itself (filters, triggers, automatic punishments). Default: on.
Include manual actionsLog actions admins perform directly in Discord. Default: on.

Events​

The events matrix lists every event grouped by category. Each event has an enable toggle and a destination select: Default (inherit the default destination), Channel (reveals a per-event channel picker), or DM.

CategoryEvents
ModerationBan, Unban, Kick, Mute/Timeout, Unmute, Warning, Message Delete, Message Edit, Bulk Delete, Role Added, Role Removed
User UpdatesUsername Change, Nickname Change, Avatar Change, Member Join, Member Leave
AutoModFilter Triggered, Spam Detected, Word Filter, Vote Ban, Captcha Failed, Captcha Completed, Secret Code Redeemed, Invite Reward Granted
GamificationQuest Completed, Level Up

Per-event routing lets you split streams — for example, Moderation events to a private admin channel, User Updates to a quieter audit channel, and Gamification events off entirely.

How it works in Discord​

Once configured, log entries flow to their destinations as events happen. Two details make the log trustworthy:

  • Native actions are attributed. When an admin bans or times someone out through Discord's own UI, the agent looks up Discord's audit log to attribute the action to the acting admin — so manual moderation is credited correctly, not logged anonymously.
  • No double logging. The agent dedupes its own actions: something the agent did (a filter deletion, a warn-limit timeout) is logged once, not again when Discord's audit log echoes it.

Actions that fail — for instance, a timeout the agent couldn't apply due to role hierarchy — are not logged as successes.

Saving your changes​

This page uses a batched save — edits stay local until you select Save in the bar that appears at the bottom of the page. Leaving the page with unsaved changes shows a warning first.

Best practices​

A log your team actually reads
  • Set the default destination to a private log channel, then override only the exceptions — it's easier to maintain than per-event channels everywhere.
  • Reserve DM routing for the events that should wake someone up (Ban, Vote Ban); everything else belongs in a channel.
  • Turn off Gamification and User Updates events in large servers if they drown out moderation entries — or give them their own channel.
  • Keep Include manual actions on: audit-log attribution is how you find out which admin took an action.
Troubleshooting

No log entries are arriving?

  • Check the master toggle, and that the Default destination isn't Don't log by default while your events sit on Default.
  • With Channel selected, a Default log channel is required and the agent must be able to post there.
  • For DM routing, make sure Admin roles for DMs is set — and that recipients accept DMs.

A specific event never shows up?

  • Check the event's own enable toggle and destination in the events matrix.
  • Agent-performed actions need Include Bot Actions on; Discord-native ones need Include manual actions on.

Manual bans show up without the acting admin?

  • Attribution relies on Discord's audit log — if you've customized the agent's permissions, it needs View Audit Log access.

On this page