Audit Log — who did what, when

What it is
The Audit Log shows a real-time trail of administrator actions taken via the dashboard: permission changes, command permission edits, manual overrides, and other administrative events. It’s the canonical place to review who made permission or dashboard changes and the exact source of those changes.

Where to look
Open Reports → Audit Log in the left navigation.

How it works / what you’ll see

• Overview counters — totals for Events, Dashboard Changes, Command Changes, and Scopes Touched.

• Tracked administrator actions — the main timeline of events; the UI supports filtering by All / Dashboard / Command and time windows (last week, etc.).

• Recent activity — details of the selected timeframe and filter; when nothing matches you’ll see an empty state.

Backend & data
The API records each audit row via a recordAuditEvent routine. Stored fields include the actor (who performed the action), the action name, target user/profile (when applicable), role/scopes affected, message/source, and a timestamp. The dashboard can fetch events for a configured window (defaulting to recent days, up to 90 days). This means the Audit Log is both human-readable and machine-backed for programmatic review.

How to use it

1. Pick a time window and filter (All / Dashboard / Command) to narrow results.

2. Review the list for each event — it shows the who/what/when and any target IDs.

3. Use the Audit Log when investigating permission changes, suspicious administrative actions, or to produce evidence for post-mortems.

Tips

• If you need an extended history, the service supports up to 90 days of lookback — but the UI defaults to shorter windows for performance. Check the date window before assuming a missing event is gone.

• Audit entries indicate whether a change was manual or generated by an automated source.

Server Statistics — live counters, snapshots & exports

What it is
Server Statistics provides live counters and time-series trend data for your Discord server: members, daily messages, boosts, voice minutes, moderation actions, and top channels/users. It also shows a preview chart and allows publishing or exporting of channel-level summaries. The dashboard surfaces an overview, short summaries, and a series (per-day) chart.

Where to look
Open Reports → Server Statistics (also labeled Server statistics in the page header).

How it works / what you’ll see

• Overview cards — total members, net growth, paid users/boosts, daily messages, and similar high-level stats.

• Server stats preview — a time-series chart with messages, joins and leaves across the chosen window.

• Summaries — quick cards such as Daily Joins, Top Command, and Poll Participation that highlight spikes and engagement.

• Settings & publishing — controls to set a summary channel and cadence for posting server summaries to a Discord channel.

• Command-driven snapshots — the /serverstats slash command family supports collect, preview, export, and settings subcommands (examples below). The server statistics view is backed by a persisted stats store so snapshots persist and can be exported.

Backend & data
The server statistics API fetches stored stats, builds per-day series and overview summaries, and enforces sensible range limits (default 7 days, clamps between 3 and 30 days). If no stats exist yet for a connected server, a default (empty) stats document is returned so the UI still renders gracefully. The service also derives helpful fields such as topChannel, topUser, moderationActions, and voiceMinutes.

Key command examples

• /serverstats collect scope:24h include:messages,joins,uptime
  Run a snapshot collection and persist it to the stats store.

• /serverstats preview scope:7d channel:#staff-updates
  Preview the latest stored statistics as an embed (helpful before publishing).

• /serverstats export scope:30d channel:#analytics
  Export recent stats as a CSV for analysis or reporting.

How to use it

1. Select a window (3–30 days, default 7 days) and the metrics you want to inspect (messages, joins, etc.).

2. Inspect the overview cards for quick health checks (e.g., daily messages, net growth).

3. Use Server Stats Preview to confirm trends and to identify spikes — drill into the summaries for context (top command, poll participation).

4. Use the /serverstats collect command to create a snapshot that persists to the stats store. Afterwards, preview or export it using the preview or export subcommands.

Tips

• The stats view is meant for both quick operational checks (daily messages / recent spike) and for scheduled publishing to staff channels for recurring reporting.

• If the server shows zeros and you expect data, confirm the bot is connected and that the server has an associated stats document (the server connection step ensures a stats doc is created).

User Lookup — inspect a member’s tracked activity

What it is
User Lookup (labeled User Lookup in the dashboard) lets staff search by Discord ID or member name to see real activity captured by GR Rocket: recent actions, warnings, command usage and other tracked events for that user. It’s useful when performing investigations, reviewing moderation history, or validating a member’s recent interactions.

Where to look
Open Reports → User Lookup.

How it works / what you’ll see

• Server summary — high-level counts (server members, members with activity, selected actions, tracked actions).

• Search box — paste a Discord ID or type a name to find the closest matches (UI shows top 5 closest matches).

• Member activity panel — once a user is selected, the page loads their recent tracked activity captured by GR Rocket: admin actions, warnings, command executions and other events.

How to use it

1. Paste or type a Discord ID or name in the search field. If you paste an ID, the lookup is exact; typing a name surfaces the top matches.

2. Select the member from the list to load detailed activity.

3. Use the results to determine a member’s recent moderation history, command usage, or to gather evidence for dispute resolution.

Tips

• Copy Discord IDs in Discord using Shift+Right-Click on a user — that ID works directly in the search box.

• Use User Lookup alongside Audit Log when you need to tie a user’s actions to a particular administrative change or event.

Workflows & best practices

• Incident triage: Start in Status (to confirm the bot and server are healthy), then use Audit Log to identify any recent administrative changes and User Lookup to inspect the involved member(s). Use Server Statistics to check if an incident corresponded with a message/joins spike. (Status page and navigation context live in Dashboard; see the Dashboard walkthrough for the Status page.)

• Weekly reporting: Schedule regular collect snapshots for /serverstats and use export to pull CSVs for deeper analysis (growth, engagement, polls).

• Permission audits: Before onboarding a new staff member, review Dashboard Permissions and then use Audit Log periodically to verify there were no unexpected permission changes.

Troubleshooting checklist

• No audit entries found — ensure your time window is wide enough and that you have dashboard access for this product/guild. The audit API enforces access checks and returns up to a configurable limit.

• Server stats are empty — confirm the bot is connected; when a server is connected, the API creates/ensures a stats document for it. If the bot was recently connected, there may not be historical data yet.

• User Lookup returns no matches — try pasting the exact Discord ID; if you used a name, pick from the top suggestions or broaden the search window.

Where this data comes from (technical note)

• Audit Log entries are persisted by the audit service and include actor, action, role/scopes, target IDs, and source metadata; events can be listed with access enforcement and a lookback window.

• Server Statistics are served by a stats service that builds an overview, summaries, and a per-day series from a persisted server stats document; the API enforces reasonable range clamps and requires dashboard access.