Some users in a Discord voice channel can use the soundboard repeatedly while others see a cooldown timer and cannot play sounds. This inconsistency is not a random bug. It is caused by the soundboard cooldown settings applied at the server level, often combined with user-specific permissions or roles. This article explains why the cooldown affects only certain users and how server administrators can control it.
Key Takeaways: Soundboard Cooldown and User Permissions
- Server Settings > Roles > Soundboard Permission: Controls whether a role can use the soundboard at all.
- Server Settings > Roles > Soundboard Cooldown: Sets the minimum seconds between soundboard uses for that role.
- Server Settings > Soundboard > Global Cooldown: Overrides all role-specific cooldowns unless a role has a lower value.
How Discord Soundboard Cooldown Works
The soundboard feature in Discord voice channels lets users play short audio clips. To prevent spam, Discord enforces a cooldown between uses. The cooldown can be set globally for the server or individually for each role.
When a user tries to play a sound, Discord checks two things in order:
- Does the user have the Soundboard permission?
If not, the soundboard button is grayed out or shows a lock icon. - What is the effective cooldown for this user?
Discord uses the lowest cooldown value from all roles assigned to the user. If no role has a custom cooldown, the server-wide global cooldown applies.
The global cooldown is set in Server Settings > Soundboard. Role-specific cooldowns are set in Server Settings > Roles > select a role > Soundboard Cooldown. If a role has no cooldown set, it uses the global default, which is 5 seconds by default.
Why Cooldown Affects Specific Users
Users see different cooldown behavior because they have different roles. For example:
- A user with the Admin role might have a 1-second cooldown.
- A user with the Member role might have the global 5-second cooldown.
- A user with the Guest role might have a 10-second cooldown.
The user with the lowest cooldown role can play sounds more frequently. Users without a role-specific cooldown inherit the global value. This is why some users experience a cooldown while others do not.
Steps to Check and Change Soundboard Cooldown for Specific Users
To fix cooldown inconsistencies, review both the global cooldown and the role-based cooldowns. Follow these steps as a server administrator.
- Open Server Settings
Click the server name at the top left of the channel list and select Server Settings from the menu. - Go to Soundboard Settings
In the left sidebar, click Soundboard. Look for the Global Soundboard Cooldown slider. This value applies to all users who do not have a role-specific cooldown. Set it to the desired number of seconds between 1 and 30. - Check Role-Specific Cooldowns
In the left sidebar, click Roles. Click the role assigned to users who experience a cooldown. Scroll to Soundboard Cooldown. If it is set to a value higher than expected, change it. To remove the role-specific cooldown and use the global value, set it to Default. - Verify User Roles
If a specific user still has issues, right-click their name in the member list and select Roles. Note all roles assigned to them. Check each role’s soundboard cooldown setting. The effective cooldown is the lowest number among all roles. - Test the Cooldown
Join the voice channel with the affected user account. Play a sound from the soundboard. Note the cooldown timer shown after the sound finishes. If it matches the expected value, the settings are correct.
If the Soundboard Cooldown Still Behaves Incorrectly
User Cannot Use Soundboard at All
If a user sees a lock icon or the soundboard button is missing, they lack the Soundboard permission. Check Server Settings > Roles > select the role and enable the Soundboard permission under Voice Channel Permissions. Also check any channel-specific permission overrides by right-clicking the voice channel > Edit Channel > Permissions.
Cooldown Is Longer Than Expected Even After Changing Settings
Discord may cache permission changes for up to 60 seconds. Ask the user to leave the voice channel and rejoin. If the issue persists, have the user restart Discord completely. If the user is on the mobile app, force close the app and reopen it.
Bot or Integration Ignoring Cooldown
Bots that use the soundboard API may have their own cooldown logic separate from Discord’s built-in cooldown. Check the bot’s documentation for its cooldown settings. Some bots bypass the global cooldown if they use a different permission model.
Soundboard Cooldown Settings: Global vs Role-Specific
| Item | Global Cooldown | Role-Specific Cooldown |
|---|---|---|
| Where to set | Server Settings > Soundboard | Server Settings > Roles > select role > Soundboard Cooldown |
| Applies to | All users without a role-specific cooldown | All users with that role |
| Default value | 5 seconds | No value (inherits global) |
| Overriding behavior | Overridden by any role-specific value | Lowest value among all user roles wins |
| Use case | Set a server-wide minimum delay | Give trusted roles faster or slower access |
Soundboard cooldown settings are separate from the Use Soundboard permission. A user needs both the permission and a valid cooldown to play sounds. If the permission is denied, the cooldown setting is irrelevant.
To check the effective cooldown for a specific user, you can use a bot that displays permission data, such as Dyno or MEE6. These bots show the resolved permissions for any user in a server, including the soundboard cooldown.
After adjusting cooldown settings, always test with the affected user account to confirm the change. If the cooldown still appears, verify that no other role or channel override is applying a longer delay.