To help you restrict who can use which features of Groovy, we've added a feature that allows you to configure permissions for users and roles.
There's a lot of commands so it's quite the time investment to configure each of those separately.
In an effort to save you some time, we've grouped similar commands into a category.
You can find which category a command belongs to on our command list below the command description:
There are four categories in total. They are:
- Add to Queue: commands that tell Groovy to play one or more songs, e.g. -play or -playlist load
- Manage Player: commands that modify how tracks are being played, e.g. -volume or -pitch
- Manage Queue: commands that change items in the queue, e.g. -move or -remove
- View the Queue: commands that require to see the current or upcoming tracks, e.g. -queue or -now playing
How it's evaluated
Groovy's permission system works fairly similarly to Discord's channel overrides.
For each role/user, you can deny or allow that role/user from using that permission. These permissions are stacked on top of each other to produce the final result. If a permission node has not been explicitly set, then it will be allowed by default.
Explicit overrides for a higher role overrides a lower role's permissions.
Setting up permissions on your server works using the perms command.
If you want to see an example of how this works, check out our guide on how to create a DJ role here.