Permissions¶
By default, everything is admin-only: anyone with Discord's Administrator permission can use
every LogDog feature, and no one else can. To hand specific capabilities to your mod team — without
making them server admins — an admin uses /permissions to grant a feature to one or more roles.
Admins only
/permissions itself can only be used by administrators — just like /setup.
Grantable features¶
Each gateable capability is a feature you can grant to roles:
| Feature | What it unlocks |
|---|---|
| Add/edit moderation reasons | The 📝 Add reason button on moderation logs. |
| Approve/deny join requests | The Approve / Deny buttons on join-request logs. |
| Ban users from the group | The 🔨 Ban / ♻️ Unban buttons and the /ban command. |
| Look up VRChat users | The /getvrcuser command. |
| View moderation history | The /getmodhistory command. |
| View moderator activity | The /getmodactivity command — audits all staff, including admins, so grant it only to roles you fully trust. |
| View the server audit log | The /auditlog command — shows all staff actions (config + moderation), including admins; grant only to trusted roles. |
Admins always have all of these — granting a role simply adds non-admins who can use it.
Using /permissions¶
Pick the feature from the autocomplete, then add, remove, or list roles:
/permissions add<feature><role>[role2…]— grant the feature to one or more roles./permissions remove<feature><role>[role2…]— revoke it./permissions list[feature]— show which roles have which features (all features, or just one). Admins are always implied.
Commands stay visible — access is checked when used
Discord can't hide a slash command based on a custom role, so grantable commands like /ban,
/getvrcuser, and /getmodhistory appear in everyone's command list. If someone without
access runs one, LogDog simply replies — only to them — that they don't have permission.
Granting the feature is what actually lets the command run.
What stays admin-only¶
The setup and configuration commands aren't grantable — they always require Administrator:
/setup, /events, /notify, /config (server feature settings, including the
ban-request channel), and /permissions itself.
See the Command reference for every command and its access level at a glance.