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.

Adding a moderation reason

For moderation events (bans, kicks, removals, and similar), each embed carries an 📝 Add reason button. Click it, type a reason, 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.

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.