Discord’s built-in integration settings let you show or hide commands for certain roles and channels, but they don’t support fine-grained control over individual subcommands. Quarky’s /permissions command fills that gap, giving server owners and administrators detailed control over which roles can use which subcommands.
Command visibility
To control which commands and channels Quarky can be used in, go to your Server Settings and open the Integrations tab. Select Quarky to manage visibility by command, channel, and role. This is Discord’s native mechanism for toggling command access at a broad level.
Command usage with /permissions
For subcommand-level control, use the /permissions command. It lets you create, view, and remove permission sets that define which roles can access which subcommands.
Create or edit a permission set
Use /permissions edit to create a new permission set or update an existing one.
Run /permissions edit and select the command you want to configure.
Select Create new to set up a new permission set, or choose an existing set to modify it.
Pick the role you want to assign permissions to.
Choose which subcommands that role is allowed to use. Save your changes when done.
You can also use /permissions edit to update an existing permission set — select the role whose subcommand access you want to change and modify the associated subcommands.
View permission sets
Run /permissions get and select a command to see all permission sets configured for it. The output lists each role alongside the subcommands it has access to.
After making any changes, run /permissions get on the affected command to confirm the permission sets look correct.
Delete permission sets
Use /permissions delete to remove permission sets you no longer need. Select the roles you want to keep — Quarky will remove the permission sets for all other roles associated with that command.
You’ll be asked to confirm before any sets are removed, giving you a final chance to review which roles will be affected.
