GuildPilot Beta
Moderation and safety

Choose one Discord channel where GuildPilot moderation commands produce public notices while preserving private staff logs and optional member DMs.

How to publish moderation transparency notices with GuildPilot

The Transparency channel makes moderation commands used in that channel visible to its Discord audience. Commands used elsewhere stay publicly silent, while private staff logs and optional member DMs remain separate settings.

Moderation - TransparencyReal dashboard
GuildPilot Transparency channel editor with an empty Discord channel selector
Select the public channel whose Discord permissions match the audience for transparency notices.Open full size

Before you start

  • Create the Discord channel where public moderation notices should appear.
  • Decide which members can view it through Discord channel permissions.
  • Configure individual moderation commands before testing.

Warning: A transparency notice can reveal the moderated member, action and reason to everyone who can view the channel. Keep sensitive evidence and staff discussion in a separate private log channel.

Publish transparency notices

1. Open Transparency channel

Open the server dashboard, select Moderation, then choose Transparency channel.

2. Choose the Discord channel

Select the text channel under Transparency channel. Discord permissions determine the audience; grant @everyone View Channel only when all members should see these notices.

3. Save the selection

Select Save transparency channel. This setting does not replace the Private staff log channel configured on each moderation command.

4. Use a moderation command in that channel

Run a configured moderation command inside the transparency channel. GuildPilot posts the public moderation message there.

5. Compare another channel

Run a reversible moderation command elsewhere. The command remains publicly silent there, although enabled DMs and private staff logging still apply.

Use a read-only public channel for published notices and a separate private channel for staff logs. Write moderation reasons that are suitable for the audience that can view the transparency channel.

Test the setup

  1. Use a designated test member and run a one-minute /mute inside the transparency channel.
  2. Confirm that a public notice appears and the private staff log remains separate.
  3. Run /unmute and confirm its expected notice behavior.
  4. Remove the test notices if they should not remain in the public record.

What a successful setup looks like

Moderation commands used in the selected channel publish a public notice there. Commands used in other channels do not publish that notice, and private logging follows each command's own configuration.

Common problems

Members cannot see the notice

Cause: Their Discord role lacks View Channel or Read Message History in the transparency channel.

Fix: Adjust the channel permission overrides for the intended audience.

A notice appears in the wrong place

Cause: The command was run in the selected transparency channel rather than a private staff channel.

Fix: Run publicly silent moderation commands outside the transparency channel, or change the saved destination.

No public notice appears

Cause: No transparency channel is saved, the command was used elsewhere, or GuildPilot cannot send messages there.

Fix: Save a current text channel and review the bot's channel permissions.

Ready to configure it?

Open your GuildPilot dashboard

Choose your Discord server, follow this guide with the live settings beside you, and save only when the preview looks right.