Staff permissions¶
Choose which Discord roles can use LogDog's moderation commands and buttons. Configure
these grants on the dashboard under Settings → Feature Permissions, or use
/permissions in Discord.
Requirements¶
| Requirement | Details |
|---|---|
| Your access | Server owner or Administrator to change grants. |
| LogDog in Discord | No additional bot permission to save grants. Channel access is managed separately in Discord. |
| LogDog in VRChat | View Audit Log for the connected group; additional permissions depend on the feature. |
| Plan | Free. |
See the permissions matrix for every feature.
Grant a feature on the dashboard¶
- Open app.logdog.gg and select your server.
- Open Settings → Feature Permissions.
- Select the Discord roles that should have access to each feature.
- Check the save result. Changes also appear in
/permissions list.
Administrators always have these capabilities. Grants add access for the selected roles; they do not restrict administrators.
Grantable features¶
| Feature | Discord capability | Command key |
|---|---|---|
| Add/edit moderation reasons | Add or edit a reason on a log message | reasons |
| Approve/deny join requests | Approve, Deny, and Deny & Block buttons | requests |
| Ban users from the group | Ban/Unban buttons and /ban |
ban |
| Look up VRChat users | /getvrcuser |
getvrcuser |
| View moderation history | /getmodhistory |
getmodhistory |
| View moderator activity | /getmodactivity |
getmodactivity |
| View the server audit log | /auditlog |
auditlog |
| Post announcements to VRChat | Discord triggers and the message Apps action | announcements |
Moderator activity and the server audit log include other staff members' actions, including administrators. Grant those views only to roles that should see that information.
Use Discord commands¶
/permissions addfeaturerole— grant a feature to up to five roles at once./permissions removefeaturerole— revoke a grant./permissions list[feature]— list one feature's grants, or all of them.
For example, select ban and @Moderators in /permissions add to let that role
use the ban command and buttons.
Dashboard access is separate¶
| Level | Discord requirement | Access |
|---|---|---|
| Owner | Server owner | Configure and manage the server in LogDog. |
| Admin | Administrator | Configure and manage the server in LogDog. |
| Manager | Manage Server, without Administrator | Read most dashboard pages. Worlds and the moderation overview require Admin. |
A feature grant does not give dashboard access. A member granted getmodhistory
can use that command but still needs Manage Server or Administrator to open a user's
dashboard history. Editing dashboard reasons requires Admin even with a Discord
reasons grant.
Channel and command visibility¶
Grant staff View Channel in your log channels separately. A feature grant does not make private channels visible or change permissions in your VRChat group.
LogDog checks access when a command or button is used. Some commands may remain visible to members without access; LogDog replies privately if access is refused. Discord's command settings under Server Settings → Integrations are separate and can also restrict commands.
What stays admin-only¶
Setup, server configuration, routing, event pings, screening configuration, Premium
assignment, and feature grants require Administrator. These cannot be delegated
through /permissions.
Members can link, reverify, and unlink their own accounts. World suggestions and
event-world buttons use the roles selected under Settings → World suggestions,
rather than /permissions. See the command reference.