Approving join requests¶
Use the buttons on a Group Request Create log in Discord to approve, deny, or block a request to join your VRChat group. Request logs include the user's profile information when it is available.
Requirements¶
| Requirement | Details |
|---|---|
| Your access | Administrator, or the Approve/deny join requests feature grant. |
| LogDog in Discord | View Channel, Send Messages, Embed Links, and Attach Files in the request-log channel. |
| LogDog in VRChat | View Audit Log and Manage Group Invites. Deny & Block also needs Manage Group Bans. |
| Plan | Free. Automatic denial through screening requires Premium. |
Configure on the dashboard¶
- Open Log Routing and route Group Request Create to a staff channel. Keep the event and its category enabled.
- Open Settings → Feature Permissions to grant staff roles Approve/deny join requests.
- Use Diagnostics to check LogDog's VRChat permissions.
In Discord, the equivalent controls are /events for routing and
/permissions add requests <role…> for staff access.
Respond to requests in Discord. The dashboard can show the request history, but does not currently offer the approve, deny, or block actions.
Respond in Discord¶
Each request log has these buttons:
| Button | Result |
|---|---|
| Approve | Accept the request so the user joins the group. |
| Deny | Reject the request. The user can request again later. |
| Deny & Block | Reject and block the user from requesting again. |
Denying or blocking opens a form for an optional reason. LogDog updates the message while it processes the action; the initial update is not confirmation that VRChat has completed it.
If someone without the required access clicks a button, LogDog tells them privately and leaves the request unchanged.
Results and failures¶
The request log records who responded and any reason they gave. The later join or rejection log also attributes the action to the Discord moderator. See Moderation reasons to edit a reason.
If VRChat rejects the action, the request log shows the error and restores its buttons. Check the LogDog account's permissions and whether someone already handled the request in VRChat. A request that has expired or was already handled cannot be answered again.
Requests answered in VRChat¶
A request can also be handled in VRChat itself, from the group's request list. LogDog notices on its next pull and updates the original request log: the Approve and Deny buttons are removed and a line such as Approved in VRChat by or Denied in VRChat by names the moderator. If a Discord moderator had already denied the request but VRChat did not apply that response, the log shows the VRChat outcome instead, and the reason they typed stays in LogDog's records rather than under the other moderator's name.
Clicking a button on a request that was already settled tells you privately that there is nothing left to do.
Withdrawn requests¶
A join request can be withdrawn by the person who sent it, or by VRChat itself, for example when they have reached VRChat's limit of 200 groups. LogDog logs this with your other request logs as Group Request Withdraw, with the reason when VRChat gives one. A withdrawn request cannot be answered. The original request log is updated the same way as one answered in VRChat: its buttons go and it reads Withdrawn, with VRChat's reason when there is one.
For automatic checks before staff review, see Request screening.