Permissions matrix¶
Use this reference to check who can configure or use a feature, what the Discord bot needs, and what LogDog's VRChat account needs in your group. Grant each permission on the platform named; Discord permissions do not grant VRChat access.
Staff and member access¶
Admin means the Discord server owner or a member with Administrator.
Manager means a member with Manage Server; Admins also have Manager access.
Granted role means a role selected in Settings → Feature Permissions or
/permissions. Those grants apply to Discord commands and buttons, not dashboard access.
| Feature | Dashboard access | Discord access |
|---|---|---|
| Setup | Admin | Admin: /setup |
| Log routing and colors | Manager to view; Admin to change | Admin: /events |
| Event pings | Manager to view; Admin to change | Admin: /notify |
| Service notifications | Manager to view; Admin to change the channel | Admin: /config → Notifications |
| Feature grants | Manager to view; Admin to change | Admin: /permissions |
| VRChat logs | Manager to browse and export | Anyone who can read the log channel |
| Moderation reasons | Admin to edit | Admin or reasons granted role |
| Bans and unbans | Manager to view/export bans; perform actions in Discord | Admin or ban granted role |
| Join-request responses | Manager to view recorded requests; respond in Discord | Admin or requests granted role |
| Request screening | Manager to view; Admin to configure | Admin: /screening |
| User lookup | Manager to search users recorded for the group | Admin or getvrcuser granted role |
| User moderation history | Manager | Admin or getmodhistory granted role |
| Moderator activity | Admin for Moderation → Stats; Manager to filter activity/log pages | Admin or getmodactivity granted role |
| LogDog activity | Manager | Admin or auditlog granted role for /auditlog |
| Group stats and instance stats | Manager; the separate Moderation overview requires Admin | Admin: /groupstats for audit-log statistics |
| Member count, open instances, instance notices | Manager to view settings; Admin to configure | Admin: /config; channel readers can see the output |
| Account linking | Manager to view; Admin to configure | Admin configures; members link, reverify, or unlink themselves |
| Role sync | Manager to view; Admin to configure | Admin: /config → Role Sync |
| Scheduled events | Manager to view; Admin to create/edit | Calendar management is on the dashboard |
| Announcements | Manager to view; Admin to publish/configure | Admin or announcements granted role to publish |
| Worlds and playlists | Admin, including browsing and reviewing suggestions | Members suggest through /suggestworld or the panel, subject to configured roles |
| Event worlds | Admin | /eventworlds and its buttons use the world-suggestion role rules; Admins always have access |
| Premium | Admin to apply/remove a slot | Admin: /premium |
Access in this table is separate from plan limits; dashboard CSV exports require Premium.
World suggestions allow everyone by default. If event-world posts are for staff only, use a private staff channel and check Who can pick worlds in settings.
Bot permissions by feature¶
For a normal logging setup, keep the invitation's View Channels, Send Messages, Embed Links, Attach Files, and Read Message History permissions in log channels. On VRChat, keep the assigned account in your group with View Audit Log.
The table below lists feature-specific requirements in addition to that setup. “No extra permission” does not remove the baseline requirement.
| Feature | LogDog in Discord | LogDog in VRChat |
|---|---|---|
| Express/Prebuilt setup | Manage Channels; LogDog must hold the permissions it sets on new channels | No extra permission |
| Routing, feature grants, Premium, viewing stored history/stats | No extra permission | No extra permission |
| Edit moderation reasons | Access to the original message and Read Message History | No extra permission |
| Ban/unban and refresh the group ban list | Message permissions in the action/ban-request channel; Attach Files for command exports | Manage Group Bans |
| Approve or deny a join request | Access to the request log message | Manage Group Invites |
| Deny & Block a join request | Access to the request log message | Manage Group Invites and Manage Group Bans |
| Request screening | Join-request logs enabled and routed to a usable channel | Manage Group Invites for auto-deny; flagging needs no extra permission |
| Event pings | A mentionable role, or Mention @everyone, @here, and All Roles in the destination channel | No extra permission |
| Service notifications | View Channel, Send Messages, Embed Links in the notification channel | No extra permission |
| Account-link roles | Manage Roles; bot role above each assigned role. View Channel, Send Messages, Embed Links in the verification channel | No extra permission; LogDog reads public profiles |
| Discord → VRChat role sync | Access to Discord role/member information; assigning linked Discord roles separately requires Manage Roles | Assign Roles and sufficient group-role rank |
| Member-count channel | Manage Channels, including permission to rename the chosen voice channel | No extra permission |
| Open-instances panel | View Channel, Send Messages, Embed Links, Read Message History in the panel channel | Join Group Instances affects which instances the account can see |
| Instance notices | View Channel, Send Messages, Embed Links in the notice channel; mention permission for pings | Instance visibility affects player counts and closure checks |
| Instance activity and turnout | No extra permission for dashboard charts | Instance visibility affects what can be recorded |
| Scheduled Discord events | Create Events; select a suitable voice channel if using one | No extra permission for Discord-only events |
| Scheduled VRChat events | No extra permission for VRChat-only events | Manage Calendar |
| Announcements to VRChat | Access to source messages; Add Reactions and Read Message History for status reactions | Manage Announcements |
| Announcement copies in Discord | View Channel, Send Messages, Embed Links in the announcement channel; mention permission for pings | Access to the source group posts |
| World-suggestion panel and event-world posts | View Channel, Send Messages, Embed Links, Read Message History in the chosen channels | No extra group permission for world lookups |
Role-triggered announcements also depend on LogDog's application-level Message Content
access. Server admins cannot grant this with a Discord role. Mention @LogDog or use
the message Apps action when role triggers are unavailable.
Where to grant access¶
- Discord bot permissions: Server Settings → Roles → LogDog's role. Check the target channel's permission overrides too.
- Discord staff access: Settings → Feature Permissions on the dashboard. Give the same staff roles access to private log channels separately in Discord.
- VRChat group permissions: Group → Settings → Roles. Enable the permission on a role and assign that role to the exact account shown in LogDog setup.
Check a permission problem¶
Open Diagnostics on the dashboard to review bot, channel, and VRChat access. An unknown status means LogDog could not verify it; it is not confirmation of access. For a role-assignment failure, also check role order on the relevant platform.
If setup could not create a private category, check Attach Files and Read Message History as well as the other requested channel permissions. Fix the category's visibility in Discord; granting a missing bot permission does not itself make an already-public category private.