Manage Roles: role hierarchy is the only thing bounding it

Manage Roles looks narrow and is not. Its real boundary is where the app's own highest role sits in your hierarchy.

Allows management and editing of roles

Discord · 2026-08-30

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52

What the bit grants

Manage Roles is bit 28, decimal value 268435456. Discord documents it as "Allows management and editing of roles".

In practice that means creating roles, editing their permissions, and assigning or removing them from members. An app with Manage Roles can grant a role any permission the app itself holds.

The hierarchy rule

An app can only act on roles positioned below its own highest role. Move the app's role to the top of the list and Manage Roles becomes close to unlimited: it can then create a role with any permission and assign it to anyone.

This is why "it only has Manage Roles" is not by itself reassuring. Where the role sits is as much of the answer as which bit is set.

It also means the safe configuration is a real one: keep the app's role directly above the roles it must manage and no higher. Reaction-role and levelling apps work fine that way.

Why so many apps ask for it

Self-assignable roles, level rewards, verification gates and ticket staff routing all need to assign roles. It is one of the most commonly requested high-risk bits in this catalog, and usually for a legitimate reason.

The thing to check is whether the app also asks for Administrator. If it does, Manage Roles is redundant: it already has it.

Decode an install link

Parsed locally. The link is never requested and nothing is authorised.