GuildPilot Beta
Getting started and administration

See who saved server settings, compare before-and-after values and filter recent configuration changes during staff reviews.

How to review dashboard change history with GuildPilot

Changes History records recent settings saved through the GuildPilot dashboard. It helps server owners understand who changed a module and which visible values were affected without exposing protected values.

Changes HistoryIllustration
Illustrated GuildPilot change timeline with staff actors and before-and-after settings
Filter recent saved updates and compare the affected settings.Open full size

Before you start

You need dashboard access. The page covers saved GuildPilot configuration updates and keeps the recent seven-day window shown in the interface; it is not a Discord message or moderation-event archive.

Review recent changes

1. Open Changes History

Choose your server, then select History → Changes History. Start with the summary and selected period.

2. Filter the results

Use Search, Module, Changed by and Period, then choose Apply filters. Clear the filters when you need the complete available window again.

3. Compare From and To

Open the relevant update and compare From with To. Protected or large values may be summarized as changed rather than displayed in full.

4. Confirm the live setting

Open the affected module and verify its current saved value. History explains the update but does not restore an earlier version automatically.

Warning: Re-entering an old value is a new configuration change. Check current server requirements before replacing a newer setting.

Test the setup

  1. With a staff test account, change a harmless fictional label in one dashboard module and save it. Open Changes History, filter to that module and confirm the actor plus before-and-after summary appear. Restore the original label when finished.

What a successful setup looks like

Recent saved updates can be filtered by area and actor, and each result provides enough context to locate the affected setting and verify its current state.

Common problems

An older change is missing

Cause: The page retains the seven-day window shown in the interface.

Fix: Use Discord logs or your own operational records when you need history beyond that window.

A value is shown as hidden or updated

Cause: GuildPilot avoids displaying protected or unsuitable full values in the audit view.

Fix: Open the affected module and verify the current value with an authorized account.

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.