Permissions

Overview

Hubdustry requests only the permissions it needs to function. Each module may require different permissions, and you can grant them granularly based on which features you use.

Required Permissions (All Modules)

These permissions are needed for Hubdustry to operate at all:

Permission	Required	Purpose
Send Messages	✅	Respond to commands and send notifications
Embed Links	✅	Display rich embeds in responses
Read Message History	✅	Context for moderation, translation, and reaction roles
Use External Emojis	✅	Display custom emoji in bot responses
View Channels	✅	Access channels where the bot is used
Use Application Commands	✅	Register and respond to slash commands

Per-Module Permissions

Leveling

Permission	Purpose
Manage Roles	Assign role rewards when members level up
Attach Files	Send rank card images

Moderation

Permission	Purpose
Manage Messages	Delete messages (auto-mod, purge)
Kick Members	Execute kick actions
Ban Members	Execute ban actions
Moderate Members	Timeout members
Manage Roles	Assign/remove roles via moderation actions
View Audit Log	Track moderation events

Music

Permission	Purpose
Connect	Join voice channels
Speak	Play audio in voice channels

VoiceMaster

Permission	Purpose
Manage Channels	Create/delete temporary voice channels
Move Members	Move members between voice channels
Manage Roles	Set channel-level permission overrides

Welcome

Permission	Purpose
Manage Roles	Assign auto-roles to new members

Reaction Roles

Permission	Purpose
Manage Roles	Assign/remove roles when members react
Add Reactions	Add initial reaction emojis to messages

Translation

Permission	Purpose
Add Reactions	React with flag emojis for translation

Common Issues

"Missing Permissions" Error

Cause: Hubdustry's role is below the target role in the hierarchy.

Fix:

1. Go to Server Settings → Roles
2. Drag the Hubdustry role above the roles it needs to manage
3. Retry the action

Bot Can't See a Channel

Cause: Channel-level permission overrides are blocking view access.

Fix:

1. Go to the channel's Permission Settings
2. Add the Hubdustry role
3. Grant View Channel permission
4. Save changes

Bot Can't Assign a Role

Cause: The target role is higher than Hubdustry's role in the hierarchy.

Fix: Move Hubdustry's role above the target role in Server Settings → Roles.

Best Practices

1. Don't grant Administrator — It's tempting but unnecessary. Grant only specific permissions.
2. Position the role correctly — Hubdustry's role should be above any role it needs to manage.
3. Use channel overrides — Restrict the bot to specific channels if you want fine-grained control.
4. Audit regularly — Check Server Settings → Integrations to see what permissions bots have.