Permissions and role hierarchy

• Server permissions come from the member's Discord roles.
• Channel overwrites can allow or deny permissions for a specific category or channel.
• Role hierarchy limits which members and roles a bot can manage, regardless of permission bits.

Grant permissions according to enabled features. Music needs voice access; logging needs access to its log channel; role-based features need Manage Roles; channel-creating features need Manage Channels.

• View Channel, Send Messages, Embed Links, and Read Message History for relevant text flows.
• Connect and Speak for music; Move Members for join-to-create or voice moderation.
• Manage Roles for verification and reaction roles.
• Manage Channels for tickets, join-to-create, and channel locks.
• Ban, Kick, Moderate, Mute, or Deafen Members only for the matching moderation actions.

Discord permissions are only one layer. A command can also require an enabled dashboard feature, an Airwavy staff or DJ role, premium access, a vote, or another eligibility rule shown in its reference entry.

• Manage Server can allow music controls when DJ-only mode is enabled, but it does not automatically grant every Airwavy feature entitlement.
• Premium and vote requirements are shown in the verified command reference.
• Feature-gated commands remain unavailable until that server feature is enabled and saved.
• Administrator includes Discord permission bits but still does not bypass role hierarchy or Airwavy-specific access gates.

• Check the bot role at server level and the effective permission overwrites on the exact text, voice, thread, or category involved.
• Application commands can be restricted by Discord at server, role, member, or channel level.
• A bot can see one channel and still be unable to send, embed, attach, connect, speak, or read history there.
• Private ticket, log, verification, and staff channels should allow only the intended people and Airwavy.

1. Identify the exact command, automation, target member, role, and channel.
2. Check the command reference for the bot permission declared by that command.
3. Inspect server permissions, then the target channel's effective overwrites.
4. Compare Airwavy's highest role with the target's highest role.
5. Retry with the same normal member account after Discord has applied the change.