logsRead-only fictional dashboard · no Discord connection
SHADOW TEAM · FICTIONAL READ-ONLY DEMO

Explore every dashboard channel safely. Controls show the real interface, but saves, uploads and moderation actions are blocked and never reach Discord.

Logs

Guided Log Studio setup
  1. 1
    Step 1Choose destinations
  2. 2
    Step 2Design your logs
  3. 3
    Step 3Review and publish
Logging status

Discord log posting

Turn logs on, then choose a text channel for each log type. Leave a log type set to None to keep it off.

Destinations 10/10
Events selected 78/78
Storage Discord only
Step 1

Channel routing

Choose where this group posts.

Log group

Messages

Keep only the events your staff needs.

5 / 5

Channel routing

Choose where this group posts.

Channel

SHADOW TEAM / logs
Block channels where messages not logged

Block channels where messages not logged

Events to post

Keep only the events your staff needs.

Step 2

Design how your logs look

Start with one shared layout for the whole server, then refine a family or a single event only when you need to.

Where should this design apply?

Global and family designs control shared layout only. Every event keeps its own data and native accent colour; choose a single event to change its colour.

Using the inherited design Nothing extra is stored here. Changes above this level continue to flow through automatically.

Message blocks

Drag blocks or use the arrow buttons. Discord’s component limits are still enforced.

HeaderEnabled
SummaryDisabled
Fact rowsEnabled
User avatarEnabled
Change listEnabled
BodyEnabled
FooterDisabled
TimestampEnabled
Link buttonEnabled

Available details

Click a detail to insert it into the selected text block. Only details valid for the sample event are shown.

Step 3

Review what will change

Check the destination, design level and sample event before publishing.

Discord destination
No channel selected
Design level
Global layout
Previewed event
Message delete
Publishing changes future log messages only. GuildPilot will not rewrite messages already posted to Discord.

Discord event logs are streamed to Discord and are not stored as event history. Dashboard configuration changes are kept separately in Changes History for 7 days. Audit-backed events require View Audit Log. Message text appears only when Discord supplies it; failed deliveries are discarded and not retried.

Account and demo settings

These preferences apply only in this browser. Demo pages use fictional data and never change a Discord server.