Permissions and role hierarchy

This is Discord's rule, not ours, and it explains most of what looks like a broken bot: Unum can only manage roles below its own highest role, and can only moderate members whose highest role sits below its own.

So a bot with Manage Roles still cannot give someone a role that outranks it, and a bot with Ban Members still cannot ban a moderator who outranks it. Permissions decide what it may do; hierarchy decides who it may do it to.

Put Unum's role at the top of your role list. That is what gives it full use of its features: it can then hand out and remove every role, and moderate every member. The one exception is the server owner, who no bot can act on.

1. 01Open Server Settings, then Roles.
2. 02Drag Unum's role to the top of the list, above your own staff and admin roles.
3. 03If you would rather not put it at the very top, it has to sit above every role it touches and above every member it moderates. Anything above it is out of reach.

Give Unum Administrator, and put its role at the top. It is the setup with the least hassle: every feature works, channel overrides stop being something you have to chase, and switching a new feature on later never needs another permission change.

Administrator is not a way around hierarchy. Unum still cannot manage a role above its own, still cannot moderate a member who outranks it, and still cannot act on the server owner. Role position is what decides those, not the permission.

If you would rather not grant Administrator, these are the permissions the work actually requires. Grant what the features you use need, and come back when you switch on something new:

Posting anything at all

View Channel, Send Messages and Embed Links in the channel concerned. Threads also need Send Messages in Threads.

Roles: level rewards, live roles, subscriber roles, role menus, auto roles

Manage Roles, plus a role position above every role being handed out.

Moderation: warn, timeout, kick, ban

Moderate Members for timeouts, Kick Members, Ban Members, and a role above the members being actioned.

Message cleanup and automod

Manage Messages and Read Message History in the channels being watched.

Tickets and temp channels

Manage Channels, since both create channels and set their permissions.

Logging

View Audit Log, so entries can name who did what.

A server-wide permission can still be denied on a single channel, and channel overrides win. If one feature works everywhere except one channel, check that channel's permissions before anything else.

For private channels (a staff-only log or a ticket category), give Unum access explicitly, either directly or through a role it has.

The dashboard opens for the server owner, Administrators and the server's Bot Manager role. A Bot Manager can use almost everything, but some settings stay with the owner and Administrators because they reach further than a Bot Manager's own Discord permissions.

• Billing, Server Groups, Custom Bot and Settings, General.
• Logging settings, Server Guard settings, reversing a Server Guard incident and the warning escalation ladder. A Bot Manager can still see all of them, lock the server down and clear a raid.

A Bot Manager sees log entries only from channels they can view in Discord. Entries from other channels stay hidden from them, and so do entries from threads and forum posts, entries from channels that have since been deleted, and channel deletions.

• Discord shows the permissions a member actually has, including the bot: Server Settings, Members, pick Unum, then look at its roles.
• For one channel, open that channel's settings and check Unum or one of its roles under Permissions.
• If a feature still refuses to act on a specific person, compare their highest role with Unum's. That is almost always the answer.