Banning users¶
LogDog can ban and unban VRChat users from your group right from Discord — no need to
open the VRChat site. Ban with a button on a warn or kick log, or with the /ban
command, and the action runs on your group within a couple of seconds.
One-time permission needed
Banning is optional, and it needs one extra VRChat permission beyond audit-log access:
the LogDog account's role must have Manage Group Bans. Until you grant it, the /ban
command and buttons still appear, but every attempt fails with a note explaining why.
Grant it the same way as audit-log access — Group → Settings → Roles → the LogDog account's role → enable Manage Group Bans. See Grant audit-log access for the full role walkthrough (the same account and the same Roles screen).
Ways to ban¶
From a log embed¶
Warn and kick events carry a 🔨 Ban button. Click it, confirm — optionally adding a reason — and LogDog bans that user from your group. Once a ban lands, the resulting Group User Ban event carries a ♻️ Unban button, so you can reverse it just as easily.
With the /ban command¶
/ban user<user_id>[reason]— ban a VRChat user by theirusr_…id./ban unban<user_id>— lift a ban./ban list— show everyone currently banned from your group.
When you ban, a confirmation appears where you can add an optional reason. It's recorded on the resulting log embed and is editable later, like any moderation reason.
Who's allowed to ban¶
By default only admins can ban. To let specific roles (like Moderators) ban too, an admin
uses /ban configure:
/ban configure add— grant one or more roles permission to ban./ban configure remove— revoke it./ban configure show— see who can ban and where ban requests post.
Requesting a ban¶
If someone without ban permission clicks the Ban button, they can instead request one: they write a short case, and LogDog posts it — @-mentioning the roles that can ban, with a Ban button for a moderator to action. Nothing happens until an authorized mod confirms.
By default the request posts in the channel it was made in. To send all ban requests to a
single dedicated channel (e.g. a private #ban-requests), an admin sets one:
/ban configure request-channel[channel]— choose the channel ban requests post to. Leave the channel empty to clear it and go back to posting where the request is made.
Make sure LogDog can post there
Give LogDog View Channel, Send Messages, and Embed Links in the dedicated channel. If it can't post there, requests fall back to the channel they were made in.
What you'll see¶
A ban you perform shows up as a normal Group User Ban log, with a Banned by (Discord) line naming who triggered it — plus your reason in the 📝 Reason field if you gave one. (The native Banned By field always names the VRChat account that carried the ban out, which is the LogDog account.)
If a ban can't be completed
LogDog posts a short follow-up that @-mentions you in the channel you used, with the reason straight from VRChat. The common ones:
- lacks Manage Group Bans — grant the permission (see the callout above).
- same or higher rank — VRChat won't let an account ban a member whose group rank is equal to or higher than the LogDog account's. Raise the LogDog account's role position, or ban a lower-ranked member.
LogDog won't ban itself
For safety, LogDog refuses to ban any of its own VRChat accounts — doing so would cut off logging for your group.