Bot permissions & role hierarchy

The permissions HoneyGate needs and the one Discord rule that trips everyone up.

HoneyGate needs a few Discord permissions to do its job. This page explains what they're for and the single most important setup step: role hierarchy.

The permissions HoneyGate asks for

When you add HoneyGate, Discord shows you the permissions it requests. The main ones are:

• Manage Roles — so it can give and remove roles (the core of almost everything HoneyGate does).
• View Channels, Send Messages, Embed Links, and Read Message History — so it can post welcomes, run games and giveaways, and show its menus.

HoneyGate asks only for what it needs — it does not ask to be a server Administrator.

The one rule everyone trips on: role hierarchy

This is the most common setup problem, so it's worth getting right once:

**A bot can only manage roles that sit below its own role in the list.**

Discord enforces this for safety. If the HoneyGate role is below a role you want it to give out, the bot physically cannot assign it — and there's no error, it just silently doesn't happen.

How to fix it

1. Open Server Settings → Roles.
2. Find the HoneyGate role.
3. Drag it up so it sits above every role you want HoneyGate to hand out (verification roles, level roles, holder roles, colour roles, and so on).

A good habit: keep HoneyGate's role near the top of your list, just under your own staff/admin roles. Then it can manage everything beneath it.

A note on channel permissions

For features tied to a specific channel (welcome messages, announcements, game posts), make sure HoneyGate can actually see and send messages in that channel. If a channel's own permissions block the bot, it can't post there even if its overall role looks fine.

Want the bot to do less?

You're in control. If you'd rather HoneyGate not touch certain roles, just keep those roles above it — they'll be off-limits to the bot by design.