Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Made one of the the Permission Hierarchy rules clearer #1036

Merged
merged 2 commits into from
Jul 27, 2019
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
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