Server audit log¶
LogDog keeps a server audit log — a running record of everything your staff does through
LogDog: configuration changes and moderation actions. View and export it any time with
/auditlog.
It answers "what's been changed/done in this server, by whom, and when?" — the server-wide, chronological companion to Moderator activity (which focuses on a single person).
Admin by default — assignable, but grant it carefully
/auditlog is admin-only by default, but an admin can grant it to specific roles with
/permissions (the View the server audit log feature). Because it exposes
every staff member's actions — including other admins — hand it only to roles you fully trust.
Using /auditlog¶
Run /auditlog — the reply is ephemeral (only you see it). Two optional filters:
user— only actions by that Discord member.category— only one kind of action:permissions,config,premium,setup, ormoderation.
What's recorded¶
Actions taken through LogDog (things done directly in VRChat show in your normal logs and moderation history, not here):
| Category | Examples |
|---|---|
| Permissions | Granting / revoking a feature to a role with /permissions |
| Config | Account-linking settings (channel, roles, toggles), the ban-request channel |
| Premium | Applying / removing LogDog Premium |
| Setup | Connecting a VRChat group, deleting the configuration |
| Moderation | Bans & unbans, approving / denying / blocking join requests, adding & editing reasons, ban requests |
What you'll see¶
A summary embed — a tally by category plus a preview of the most recent ~12 entries, each
showing when (in your local time), who, the action, and the target it affected —
and an attached audit-log-<server>-YYYYMMDD.csv with the complete record. Open the CSV in Excel
or Google Sheets to sort, filter, and search:
| column | what it is |
|---|---|
timestamp_utc |
when it happened (UTC, sortable) |
actor |
who did it (Discord name) |
actor_id |
their Discord user ID |
action |
the action key, e.g. permissions.grant, moderation.ban |
target |
what/who it affected (a role, channel, user, …) |
detail |
extra context for the action |
How far back does it go?
The audit log is kept for 90 days, then older entries are aged off automatically.
Related¶
- Moderator activity — the per-person view: everything one moderator/admin has done.
- Permissions — how granting features (including this one) to roles works.
- Command reference — every command and its access level.