Configure audit-log delivery

Clan Labs saves supported audit events to the dashboard audit log. Delivery settings independently control whether each event type also produces a Discord embed and where it is sent.

Before you startCopy link to Before you start

• The bot is installed and active.
• A default audit channel exists.
• Clan Labs can view and send embeds in every destination channel.
• You are an Owner or the Discord server owner.

StepsCopy link to Steps

1. Open the community’s audit or channel settings and select the default audit-log channel.
2. Open Manage delivery.
3. Search for and select one or more audit event types.
4. Choose Use default channel, Send to another channel, or Don’t send to Discord.
5. When using a custom channel, select a text-capable destination.
6. Apply the change to the selected event types.
7. Save the community settings.

An exception can be changed or removed later. Removing it returns that event type to the default channel behavior.

Check the resultCopy link to Check the result

The summary reports how many event types use the default, a custom channel, or no Discord embed. Events remain available in Audit Logs even when Discord delivery is suppressed.

Perform one safe action for a configured event type, such as a test warning that you then remove. Confirm the audit entry appears in the dashboard and that the Discord embed follows its delivery rule.

• Put sensitive moderation audits in staff-only channels.
• Remember that suppressing a Discord embed does not erase the dashboard record.
• Review access to webhook-like delivery channels and avoid exposing member details publicly.
• Use retention and rollback controls only through the dashboard.

Common errorsCopy link to Common errors

• The dashboard entry exists but Discord has no embed — the event may be suppressed or the default delivery may be disabled.
• A custom destination says Stored channel — the channel is no longer in the current Discord resource list.
• Delivery fails after a channel change — check View Channel, Send Messages, and Embed Links on that channel.
• No audit entry exists — confirm the action is one of the supported audited workflows and that you are viewing the correct community and date range.

Next, learn Audit logs and rollback or configure events.