Approving join requests¶
When someone asks to join your VRChat group, LogDog posts a Group Join Request log. LogDog lets you approve or deny that request right from Discord — no need to open the VRChat site. Click a button on the request log and the decision lands on your group within a couple of seconds.
Know who's knocking
Request logs are automatically enriched with the requester's avatar, age verification,
trust rank, and bio, so you can vet them before deciding. Want the full profile? Use
/getvrcuser.
One-time permission needed
Responding to join requests is optional, and it needs one extra VRChat permission beyond audit-log access: the LogDog account's role must have Manage Group Invites. Until you grant it, the 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 Invites. See Grant audit-log access for the full role walkthrough (the same account and the same Roles screen).
Ways to respond¶
Every Group Join Request event carries three buttons:
- ✅ Approve — accept the request; the user joins your group.
- 🚫 Deny — reject the request. The user can request again later.
- ⛔ Deny & Block — reject and block the user, so they can't request again.
Click Approve and the request is accepted immediately. Click Deny or Deny & Block and a short form pops up where you can add an optional reason before confirming.
The embed updates the instant you click — it marks who approved or denied it and removes the buttons — and the action runs on your group within a couple of seconds.
Who's allowed to approve or deny¶
By default only admins can respond to join requests. To let specific roles (like
Moderators) respond too, an admin uses /request-access:
/request-access add— grant one or more roles permission to approve/deny./request-access remove— revoke it./request-access show— see which roles can respond.
If someone without permission clicks a button, LogDog quietly tells them they're not allowed — nothing happens to the request.
What you'll see¶
The request log updates in place with a ✅ Approved by or 🚫 Denied by line naming who made the call — plus your reason in the 📝 Reason field if you gave one when denying (editable later, like any moderation reason).
When the user actually joins (after an approval) or the request is rejected, that follow-up event also carries an Approved by (Discord) / Denied by (Discord) line, so the attribution shows up wherever those events land.
If a response can't be completed
If the VRChat call fails, LogDog edits the request log back to a short "⚠️ Couldn't approve / deny" note with the reason straight from VRChat, and restores the buttons so you can try again. The common ones:
- lacks Manage Group Invites — grant the permission (see the callout above).
- already handled — the request was already approved or denied (often directly in VRChat, or it expired). Nothing more to do.