Reading your logs

Every event LogDog delivers is a Discord embed. Once you know the layout, each one tells you who did what, to whom, and when — at a glance.

Anatomy of a log embed

• Author line (top) — your group's name, short code, and icon. Click it to open the group on VRChat.
• Title — the event, in plain language (e.g. Group Member Join, Group User Ban).
• Color — the event's severity:
  • Informational — routine activity.
  • Warning.
  • Negative action — bans, kicks, removals.
  • Positive action — joins, accepts, unbans.
  • Gray action — neutral/administrative.
• Fields — the details for that event: the user(s) involved (linked to their VRChat profiles), who performed the action, roles, instance/world info, and so on.
• World image — instance events include the world's picture when LogDog has it cached.
• Footer — the VRChat user IDs involved and the audit Log ID, plus the timestamp.

User and world names are clickable links to their VRChat pages wherever LogDog has an ID.

What the user embeds add

Events about a user (joins, requests, invites, leaves, bans, unbans, kicks, warnings, removals) carry a small profile so you can judge them without leaving Discord:

• The user's avatar, trust rank, age verification, and when they joined VRChat. Joins, requests and invites also show the bio; moderation actions leave it out.
• In your Discord: the linked Discord account, only when the user has linked.
• Member since (or Before LogDog was added for older members) and Group history: a headline such as Returning: left 3 months ago or Previously banned, with this group's counts in parentheses (joins, leaves, requests, denied).
• Moderation history: warns, kicks, bans and unbans in your group, left out when all are zero.
• A Moderation History button (or User History on joins, requests, invites and leaves) to that user's page on the dashboard.

What the instance embeds add

• Instance open shows the world, its access type, region and capacity, the world picture, and a Last Visited line when your group has hosted that world before (with that session's peak).
• Instance close adds the session: Open for, Peak and Average players.
• Both carry a View Instance Stats button to the recorded session on the dashboard's Group Stats page (Not recorded yet if the poller had not seen it).

The Timestamp is always the last line, rendered in your own time zone, and when a moderation reason has been added, the Reason line sits directly above it.

Adding a moderation reason

For moderation events (bans, kicks, removals, and similar), each embed carries an Add reason button. Click it, pick a reason or type one, and it's recorded on the embed — showing who added it (and who last edited it). It's a lightweight way to keep your "why" attached to the "what," right in the channel.

The modal offers a dropdown of reason presets: LogDog's starter set (Racism, Harassment, Underage, Spam or advertising, Breaking instance rules, Disrespecting staff, and for join requests Not 18+ and Did not meet the requirements), or your own. Custom is selected by default, so typing works exactly as before; with a preset picked the text box is optional and anything you type becomes a detail line under it. Admins edit the list under /config → Moderation → Edit reason presets (one per line; add (requests) or (moderation) after a reason to offer it only there) or on the dashboard's Settings → Reason presets card, with Restore defaults to get the starter set back. Free servers keep up to 10 presets, Premium up to 25.

Reasons can also be added or edited from the dashboard: open the event in VRChat Audit Logs and use Add reason / Edit reason in its drawer. The Discord message updates either way.

By default only admins can add or edit reasons. To let specific roles (like Moderators) do it too, an admin grants the Add/edit moderation reasons feature with /permissions:

• /permissions add reasons <role…> — grant one or more roles access.
• /permissions remove reasons <role…> — revoke it.
• /permissions list reasons — see who currently has access.

Act on it, too

Warn and kick embeds also carry a Ban button, and ban embeds carry Unban — so you can action a moderation event without leaving Discord. See Banning users.

See a user's whole record

Admins can pull one user's entire moderation history — every warn, kick, ban, and request outcome in your group — with /getmodhistory.

Get pinged on important events

Don't want to watch the channel? Use /notify to have specific events (like bans or member removals) @-mention a role when they happen — so your team is alerted the moment it matters.

Where events land

Which channel an event appears in depends on the layout you picked in /setup:

• Express — requests, instance activity, and everything else split across three channels.
• Prebuilt / Custom — routed by category to the channels you chose.

You can re-route any event or whole category to a different channel at any time with /events (the Channel button) — no need to re-run setup. See /events and Managing your configuration.