How to configure Discord server logs with GuildPilot

GuildPilot streams selected server events to dedicated Discord text channels. It supports message, voice, member and moderation, invite, and Discord AutoMod action groups, but it does not retain a browsable event history in the dashboard.

Before you start

• Create private Discord text channels for the event groups you want to keep.
• GuildPilot must be able to view and send messages in each destination.
• Grant View Audit Log for events that rely on Discord audit entries.
• Enable Message Content Intent when message text should be available and Discord supplies it.

Warning: Log messages can contain member, moderation and message context. Restrict each destination to the staff who should see that information.

Configure server logs

1. Open Logs and enable delivery

Open the server dashboard and select Logs. Under Discord log posting, turn logging on.

2. Configure message and voice destinations

Choose a text channel for Message logs and Voice logs. Leave a group set to None when you do not need it.

3. Configure members, invites and Discord AutoMod

Choose channels for Members & moderation, Invite logs and AutoMod. The AutoMod group here records actions taken by Discord AutoMod rules; it does not enable GuildPilot's unfinished AutoMod configuration page.

4. Choose event types and exclusions

Under Events to post, select only the events required by your staff workflow. Configure Ignore bots and Block channels where messages not logged when supported by the selected group.

5. Save the destinations

Select Save changes. GuildPilot begins streaming new matching events; it does not backfill earlier events.

Recommended configuration

Use separate destinations for message logs and member/moderation logs so permissions and noise can be managed independently. Select only events staff will review and act on.

Test the setup

1. Trigger a reversible event, such as editing a fictional message or joining and leaving a voice channel.
2. Confirm that the selected destination receives the matching GuildPilot log.
3. Verify that an unselected event group or blocked channel does not post.
4. Delete the fictional test message and log entry if your policy does not require keeping them.

What a successful setup looks like

New selected events appear in their configured Discord channels with the context Discord supplies. Groups set to None remain off, and the dashboard does not present stored event history.

Common problems

An audit-backed event has no actor

Cause: GuildPilot lacks View Audit Log or Discord did not provide a matching audit entry.

Fix: Grant the bot View Audit Log and test a new event. Not every event is guaranteed to have an audit actor.

Message content says unavailable

Cause: Discord did not supply the content or Message Content Intent is disabled.

Fix: Enable the intent when appropriate and test a new message event. GuildPilot does not reconstruct unavailable content.

A failed log never appears later

Cause: Failed deliveries are discarded and not retried.

Fix: Correct the destination permission or channel, save the page and test with a new event.

Old events are absent

Cause: Logging streams new events only and is not a stored dashboard audit history.

Fix: Use your Discord log channels and their retention settings for historical review.