Permissions

Permissions are essential in managing your Discord server and keeping it secure. They allow you to control what members can and cannot do within your server. This guide will help you understand how to set up and manage QuaBot's permissions effectively.

Required Permissions

To ensure that QuaBot functions correctly, it needs the following permissions:

IMPORTANT

We recently added the 'View Audit Log' as a required permission. This will be used for additional moderation features, please enable this permission for the QuaBot role to unlock QuaBot's full potentional. It will continue to work without this permission.

• View Audit Log: Allows QuaBot to view additional logs for moderation purposes.
• Manage Server: Allows QuaBot to manage server settings and configurations, including automod.
• Manage Roles: Enables QuaBot to create, edit, and delete roles as needed for moderation, lockdown, and other features.
• Manage Channels: Allows QuaBot to create, edit, and delete channels for various functionalities such as tickets.
• Kick Members: Permits QuaBot to kick members from the server when necessary (moderation).
• Ban Members: Permits QuaBot to ban members from the server when necessary (moderation).
• Change Nickname: Allows QuaBot to change its nickname in the server for better identification. (optional)
• View Channel: Allows QuaBot to see channels and read messages for audit logs and more.
• Moderate Members/Timeout Members: Allows QuaBot to timeout members for moderation purposes.
• Send Messages: Enables QuaBot to send messages in channels for communication and notifications.
• Create Public Threads: Allows QuaBot to create public threads for discussions, tickets and suggestions.
• Create Private Threads: Allows QuaBot to create private threads for discussions, tickets and suggestions.
• Send Messages in Threads: Enables QuaBot to send messages in threads for communication and notifications.
• Manage Messages: Allows QuaBot to delete messages and manage messages for moderation purposes.
• Pin Messages: Allows QuaBot to pin messages, used for various functions including pinning messages in tickets.
• Manage Threads: Allows QuaBot to archive, unarchive, and delete threads for better organization.
• Embed Links: Allows QuaBot to send embedded links in messages for better presentation.
• Attach Files: Enables QuaBot to attach files in messages for sharing documents and images.
• Read Message History: Allows QuaBot to read past messages in channels for context and moderation.
• Add Reactions: Enables QuaBot to add reactions to messages for starboard and various other modules.
• Mute Members: Allows QuaBot to mute members in voice channels for moderation purposes.
• Move Members: Allows QuaBot to move members between voice channels for moderation purposes.

We highly recommend granting these permissions to ensure that QuaBot can operate smoothly and provide all its features. You can also give QuaBot Administrator permissions, which will automatically grant all the necessary permissions, although this is not required, and not enabled by default if you installed the bot after Dec 15, 2025.

Warning

Never give Administrator permissions to bots or users you do not trust. Administrator permissions allow full control over the server, which can lead to potential security risks if misused.

QuaBot Role Position

For QuaBot to manage roles and channels effectively, its role must be positioned above the roles it needs to manage. This is crucial for features like reaction roles, where QuaBot needs to assign or remove roles from members. You can adjust the role position in your server settings under the "Roles" section by dragging the QuaBot role to the appropriate position. You can see an example below:

The QuaBot role is noted as "Being managed by an Integration". Make sure it's above the roles it needs to manage or assign. It can always mention a role (if it has the permission to do so) so if you only mention roles (for example in suggestions or tickets) it does not need to be above them.

The bot can only assign roles to members if the bot's role is ABOVE the top role of that member.

Example:

John has the Member role with is the 5th role. QuaBot's role is 4th, it cannot assign any roles to John.

Command Permissions

QuaBot has multiple ways to grant permissions to use certain features and it might be a bit confusing.

Default Permissions

Some commands are restricted to certain permissions by default by the bot itself, such as /lockdown being restricted to Administrator, Manage Server and Manage Channels. You can overwrite these default permissions with Discord's Integrations permission manager, as explained below. Other commands, such as Moderation Commands are managed by the bot itself and can be controlled by integration permissions as well as the dashboard.

1. Handle permissions via Integrations

You can manage each QuaBot command's permissions via Discord's built-in integration system. This allows you to specify which roles or members can use specific commands. You can even restrict commands to certain channels if needed. Here's how to do it:

1. Go to your server settings and click on Integrations, then select the QuaBot bot.

2. Click on the command you want to manage permissions for out of the list. This list shows all QuaBot commands, excluding subcommands (Eg. /suggestion create will only show /suggestion).

3. From here, you can add or remove roles and members to control who can use the selected command. You can also restrict the command to specific channels by selecting "Only in selected channels" and choosing the desired channels.

2. Handle moderation permissions via QuaBot Dashboard

For moderation commands, you can/need to manage permissions via the QuaBot Dashboard. This allows you to set up roles that can use moderation commands like kick, ban, mute, etc, as well as permissions that are allowed to use it. This allows for more customization and is more accesible for some users. On top of these, the Discord Permissions apply as well. Users only need to have one of the roles assigned to them, or have any of the permissions, to be able to use moderation commands. Here's how to set it up:

1. Visit the configuration page of the Moderation module in the QuaBot Dashboard. Not sure how to get there? Check out our Getting Started Guide. Once there, navigate to the "Commands & Permissions" tab.

2. In this tab, you will see a list of commands that are part of the Moderation module. You can select which commands you want to enable or disable by toggling the switch next to each command. But we want to change permissions, so you need to click on the cogwheel icon next to the command you want to manage permissions for to open the permissions & roles dropdown.

3. Finally, you can select the roles and permissions that will allow users to use the selected command. Users only need to have one of the roles assigned to them, or have any of the permissions, to be able to use the command. Make sure to click "Save Changes" at the bottom when you're done.

3. Button & Select Menu Permissions

Some commands and modules, like suggestions and some others use buttons and select menus to interact with them. These interactions do not show up in the integration command list and cannot easily be managed. Most of the time these are a part of moderation for example, and they will inherit the required permissions from those commands. Other cases, like suggestions, will use a list of default permissions that the user needs to have to be able to use them. Most of the time these permissions are:

• Administrator
• Manage Messages
• Manage Server

Each module that uses buttons or select menus will sometimes have a list of permissions that are required to use them in their documentation. If you cannot find it, please reach out to our support server. We hope to replace this with a better system in the future but since we cannot manage these permissions in Discord itself we opted to do this instead of configuring each button and select menu individually.

Do you need additional support?

Most commands should have either of these two ways to manage permissions, but some commands might only have one of them. If you have any questions or need help, feel free to reach out to our support server. We're here to help you get the most out of QuaBot!