Skip to content

Commit

Permalink
Made one of the the Permission Hierarchy rules clearer (#1036)
Browse files Browse the repository at this point in the history
* Permission hierarchy is now clearer

* Updated per suggestion

Co-Authored-By: Florian Spieß <[email protected]>
  • Loading branch information
2 people authored and msciotti committed Jul 27, 2019
1 parent 59b588d commit 1f10e5a
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/topics/Permissions.md
Original file line number Diff line number Diff line change
Expand Up @@ -62,7 +62,7 @@ Note that these internal permission names may be referred to differently by the

How permissions apply may at first seem intuitive, but there are some hidden restrictions that prevent bots from performing certain inappropriate actions based on a bot's highest role compared to its target's highest role. A bot's or user's highest role is its role that has the greatest position value in the guild, with the default @everyone role starting at 0. Permissions follow a hierarchy with the following rules:

* A bot can grant roles to other users that are of a lower position than their highest role.
* A bot can grant roles to other users that are of a lower position than its own highest role.
* A bot can edit roles of a lower position than its highest role, but it can only grant permissions it has to those roles.
* A bot can only sort roles lower than its highest role.
* A bot can only kick/ban users whose highest role is lower than the bot's highest role.
Expand Down

0 comments on commit 1f10e5a

Please sign in to comment.