> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vetox.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Dashboard Watcher

> An audit trail of every configuration change made through the Vetox dashboard — who changed what, and when.

[Logging](/en/moderation/logs) records what happens **in Discord**. Dashboard Watcher records what happens **in the dashboard** — settings changes, and who made them.

<Info>
  Free on every tier. Always on — there is nothing to enable.
</Info>

## The screen

A filterable table with six columns: **Timestamp**, **User**, **Module**, **Action**, **Changes** and **Time**.

Each entry reads as *"Updated* {module}*"* with the specific action recorded as enabled, disabled, updated, reset, added, removed or reordered. The **Changes** cell opens a popover listing exactly which settings moved and what they moved to.

## Filters

| Filter     | Options                                                              |
| ---------- | -------------------------------------------------------------------- |
| **Module** | All modules, or one specific feature                                 |
| **Time**   | All time, last 7, 30, 60 or 90 days                                  |
| **Search** | Free text across the user, the module, and the changed setting names |

Ten entries per page.

<Note>
  The module filter is an **exact match**, not a partial one. Pick from the dropdown rather than typing a module name into the search box.
</Note>

## Retention — read this before you rely on it

<Warning>
  Dashboard Watcher keeps the **most recent 500 entries per server**, for up to **90 days**. Whichever limit is reached first wins.

  On an active server with several staff, 500 entries can be **days**, not months. Older entries are discarded permanently and cannot be recovered.
</Warning>

<Warning>
  This history is held in fast storage with **no database backup**. It is an operational audit trail, not a compliance record. If you need a permanent record of configuration changes, export what matters as you go.
</Warning>

## What is and is not recorded

Recorded: Server Setup, Anti-Raid, Server Insights, Self-Roles, Auto-Roles, Embed Messages, Auto-Reply, Moderation Actions, Access Control, Language, Leveling, Protection, Welcomer, Logging, Commands, Auto-Moderation, Suggestions, Temp Voice, Auto-Interaction, Giveaways, Tickets, and the Twitch, Kick, Reddit, Bluesky and Steam notification platforms.

<Warning>
  **Several features produce no audit entry at all.** Changes to them are saved correctly but leave no trace here:

  Applications · Starboard · Counting · Battle Pass · Streaks · Colors · Reminders · AI Auto-Mod · AI Server Control · AI Usage · and the YouTube, RSS and Podcast notification platforms.

  If you are investigating a change to one of those, this page will not help you.
</Warning>

<Note>
  Entries are written only when a change **succeeds**. A rejected or failed save leaves no entry, so an absence here means the change did not take effect — not that it was made secretly.
</Note>

## Dashboard Logs

A second page, **Dashboard Logs**, shows the same activity as a plain chronological list without filters or pagination. Dashboard Watcher is the fuller view — use it unless you specifically want the simple list.

## When to use it

<AccordionGroup>
  <Accordion title="A setting changed and nobody admits to it">
    Filter by the module and read back. Every recorded change is attributed to a person.
  </Accordion>

  <Accordion title="Something broke after a config change">
    Filter to the last 7 days to see everything that was touched, and work backwards.
  </Accordion>

  <Accordion title="You delegated access and want to review it">
    Pair this with [Access Control](/en/server-management/dashboard-permissions) — grant by section, then confirm here it is being used as intended.
  </Accordion>
</AccordionGroup>

<Note>
  Dashboard Watcher does not record actions taken with slash commands in Discord. Those appear in [Logging](/en/moderation/logs) instead.
</Note>