Modbot Docs
Moderation

Audit log

The Audit log page, what goes into it, how to filter it, and the difference between the audit log and the operational log permissions.

The Audit log page is one timeline of everything Modbot has recorded: bans, kicks and role changes from VRChat, people coming and going in instances, Discord events, case files, and Modbot's own record of sign-ins, settings changes and sync problems. Each row is written as a sentence, and every name in it opens a popup.

Two permissions, one page

What you see depends on two separate permissions. The page opens if you have either.

PermissionWhat it shows
See the audit logModeration and member history: who did what to whom.
See the operational logModbot's own record of how it is run: sign-ins, settings, accounts, sync problems.

The split is on purpose. A moderator who needs to see bans does not need to see that the owner changed the email settings or which API keys exist. The server removes what you may not see from every request, so you cannot get around it by editing the page address.

The Log filter offers only the logs you may see.

What each one covers

See the audit log:

  • joins, leaves, bans, unbans, removals from the group, role changes and invites;
  • the rest of VRChat's group audit log: instance kicks and warns, join requests, group posts, instances opened and closed, calendar events, changes to group details;
  • Modbot's own entry for an instance that ended on its own ("The Black Cat #39047 ended on its own"): VRChat records a close only when a moderator closes an instance by hand, so this is the entry for one that emptied out and left the group's list. Modbot writes it once VRChat's audit log has been read past the end, so a close by hand that arrives late is never labelled this way. Instances that ended before Modbot began reading the audit log get it too, because any close by hand from then cannot be known;
  • profile changes and the 18+ verified mark, including changes a moderator made by hand;
  • instance joins, leaves, avatar changes and "already here" reports from companions;
  • Discord joins, leaves, bans, kicks, timeouts, nickname and role changes, voice, deleted messages, and channel and role changes;
  • Discord account links, and the roles given or taken because of them;
  • case files written, edited, withdrawn and profile snapshots taken again;
  • evidence attached, taken off, viewed, downloaded and destroyed (these also need View evidence, because each entry names the file);
  • reviews opened and closed;
  • moderation rule flags, dismissals, and messages deleted or timeouts given by a rule;
  • replies, mentions and quotes of the group's Bluesky account, with who wrote them, what they said and a link to the post.

See the operational log:

  • sign-ins, failed sign-ins, password, username and contact changes, "sign out everywhere";
  • staff accounts created, invited, disabled, enabled, and their roles changed; reset links;
  • Modbot roles created, changed and deleted;
  • API keys and webhooks;
  • settings changes, including the ban reason list and moderation rules;
  • sync failures, rate limit stops, database updates and old data being removed;
  • AI spend limits being reached;
  • Discord bot commands run and log messages posted.

Anything Modbot cannot name, if it came from VRChat's group audit log, counts as moderation history.

Reading a row

ColumnWhat it shows
WhenThe time, with the date under it. Hover for the full date and time. A range such as ~14:05–14:20 means Modbot knows it happened between those times but not exactly when, for example a change a sweep noticed.
SourceWhere the entry came from (see below).
What happenedA sentence naming who did what to whom, and where. Hover to see the entry's type.

Click a row (anywhere that is not a name) to open it. Under the row: every field the entry holds (type, log, source, when, when it was recorded, who it is about, who did it, the world and instance, who reported it, the description, the entry id); a Changed table with each field's before and after for entries that record a change; the Snapshot the entry stands for, where it is one; and the entry's Payload and the whole Entry as JSON, each with a copy button. Click the row again to close it.

For a profile changed or profile recorded entry, the snapshot is the person's VRChat profile as it stood after that change, and Open in the person popup opens them on their Profile changes tab at that version. The words VRChat profile in the sentence do the same.

Every name in a row opens that person, whichever kind of account it is: a VRChat name, a Discord name, or the Modbot account a sign-in or a settings change is recorded against. All three open the same person popup, which shows every account Modbot can tie to the one you clicked, and the Account tab there is everything that Modbot account did and everything done to it.

Which avatar somebody switched to

An avatar change names the avatar:

Ada switched to the avatar “Nardoragon”.

The name is the whole of what anybody can know. VRChat's log gives an avatar's display name and never an avatar id, so Modbot cannot tell two avatars called the same thing apart, and an avatar that has been renamed reads as a different one. Entries from before Modbot kept the name, and entries whose log line Modbot could not read with certainty, say Ada changed avatar and cannot be filled in later.

How long somebody had been in the instance

A kick out of an instance can say how long that person had been standing there:

Mira kicked Ada out of The Black Cat #39047 after 12 minutes in the instance.

Modbot only knows this while a companion was reporting from that instance. Presence comes from companions, not from VRChat, so a kick in an instance nobody from your team was in carries no time at all.

The entry saysWhat it means
after 12 minutes in the instanceA companion watched them walk in and was still reporting when they were kicked. This is exactly how long they were there.
after at least 12 minutes in the instanceNo companion saw them arrive — one turned up later and found them already there. They had been there at least that long, and nobody knows how much longer.
nothingNobody's companion was reporting that instance at the time, so Modbot does not know. It shows nothing rather than a zero or a guess.

The same rule decides it that decides who Live believes is in an instance: see When a moderator counts as watching. A gap in watching starts the count again — if your companion stopped and another moderator's found the person there an hour later, the entry says at least the time since that later moment, not the whole hour.

The time is worked out when the kick is recorded and kept with the entry, so it stays the same however long afterwards you read it — presence entries are removed long before kicks are, and the kick keeps the answer regardless. It also means a companion that was offline and sent its reports in hours later is too late for the kicks in between, which then say nothing.

Only kicks out of an instance carry a time. Bans and removals from the group are not instance events and have no instance to measure against — but VRChat usually writes an instance kick beside them when the person was in one of your instances, and that entry, shown in the same row under Same decision, carries the time.

Who reported it

An entry a companion reported carries Reported by and the moderator whose companion it was, under the sentence. It is on the row, on the Activity tab of a person popup and on the Activity tab of an instance popup.

Where several companions saw the same thing, all of them are named, in the order their reports arrived. Modbot keeps one entry per event — six moderators in one instance all see the same person walk in, and counting that six times would wreck every figure built on it — but it now remembers who else reported it. Two companions agreeing is better evidence than one, which matters when somebody disputes what an entry says.

Open the row and Reported by lists each one with the time its report reached the server.

Entries from any other source have no reporter: a ban read out of VRChat's audit log or a setting changed in Modbot has a source, not a companion.

One decision, several entries

Some single decisions are written down more than once. Banning somebody who is standing in one of your group's instances makes VRChat record a ban and an instance kick, a second apart. A ban pressed in Modbot is recorded by Modbot, naming who pressed it, and by VRChat, which can only say "Modbot". A Discord ban arrives as a ban and a leave.

Modbot shows those as one row, with a badge such as 2 facts beside the sentence. Open the row and a Same decision block lists the other entries; click one to open everything it holds, the same as any other entry.

Nothing is hidden: every entry is still there, and anything that counts actions — the repeat offender list and the reviews — counts the decision once rather than twice.

If you filter to a kind of entry that is usually shown inside another, such as Kicked from an instance, those entries appear as rows of their own.

The sources:

SourceMeaning
VRChatVRChat's own group audit log. Exact.
SyncModbot noticed a difference between two reads of the member or ban list. It has a time window and no "who".
Companion AppA moderator's companion.
DiscordSeen by the Discord bot.
ManualEntered by a person through Modbot, such as a case file or a change to the 18+ verified mark.
ModbotSomething that happened inside Modbot, such as a sign-in or a settings change.
ImportOlder rows only. Imported records used to carry this; each one now carries the source it really came from. See Importing old data.

Filtering

Filters are chips above the table. Press Filter (or f), pick what to filter by, then pick the values. Each chip reads as a sentence: Source · is any of · VRChat, Discord, Companion App. Click the middle word to switch between is and is not; click the values to change them; click × to remove the chip. Chips combine: an entry must match every one. Clear removes them all.

By default the log shows VRChat, Discord, Companion App and Import and leaves Sync out, because sync entries have a time window and no "who". Import stays on so rows imported before records carried their own source are still there. Add Sync back by editing the Source chip.

FilterValues
SourceAny of the sources below.
TypeThe entry types you are allowed to see.
LogModeration or Operational.
Done byOne person, from the people who did the most in the last 90 days (with their count), or an id you type.
AboutOne id, for example a VRChat user id.
WorldOne world id.
Instance numberOne VRChat instance number.
WhenA day, or a stretch of days. Both ends are included.
TimeExact, or A window (a change a sweep noticed between two reads).
Somebody namedYes for entries that say who did it, No for the rest.
TextA word or phrase anywhere in the entry, its ids included.

The filters are part of the page address, so a copied link opens the same view for somebody else, and the page remembers the filters you last used.

The page shows 50 entries at a time. Load more at the bottom fetches the next 50.

Keyboard

KeysDoes
j / kMove down and up the rows.
EnterOpen or close the selected row.
oOpen the person or instance the selected row is about.
fAdd a filter.
g then aOpen the audit log from any page.
Ctrl+K (⌘+K on a Mac)Search people, worlds and pages, and run actions.
?Every shortcut that works on the open page.

Letters never fire while you are typing in a box.

The page does not refresh by itself. Change a filter or reload to see new entries.

A person's own entries are also on the Activity tab of their person popup, and an instance's on the Activity tab of its instance popup.

Where the timeline starts

Above the table: Oldest recorded entry: and a date. Anything older than that is not in Modbot. While Modbot is still reading older entries from VRChat's audit log, it adds catch-up still running.

VRChat's group audit log only reaches back a limited time. Modbot keeps what it has read from then on, for as long as your retention settings allow. See Data and retention.

How quickly things appear

Modbot reads VRChat's group audit log every 8 seconds while things are happening. When nothing new comes in, it slows down step by step, to once every 5 minutes at the slowest. These are the defaults; Settings, Sync, Group audit log shows the numbers your Modbot uses.

Companion and Discord entries arrive as they are reported.

What the audit log does not contain

  • Why somebody was banned. VRChat's audit log has no reason. Write a case file.
  • Warnings. Modbot cannot warn anybody yet.

A kick, ban or unban made from Modbot appears twice, and the two entries say different things. Modbot's own entry names the moderator who pressed the button and the reasons they picked; VRChat's entry, which arrives with the next audit-log sync, says only that Modbot's account did it. VRChat records every action Modbot takes as Modbot's own account, so the moderator's name exists in Modbot's entry and nowhere else.

Modbot is not endorsed by or affiliated with VRChat Inc. or Discord Inc. VRChat is a trademark of VRChat Inc. Discord is a trademark of Discord Inc. SteamVR is a trademark of Valve Corporation. Windows is a trademark of Microsoft Corporation. Docker is a trademark of Docker, Inc. PostgreSQL is a trademark of the PostgreSQL Community Association of Canada. Railway is a trademark of Railway Corp. Other names are trademarks of their respective owners; see Legal. Modbot and its logo are trademarks of the Modbot project. Open source under AGPL-3.0.

On this page