Fix the hierarchy of role permissions so they work again.
I don't know when Discord thought it were a good idea to change a very basic feature of how roles are handled on servers. But previously it were very logical.
So the server I run I have two main roles.
One is a member role that grants people permission to participate in X channels. (So that new members of the server doens't see all of it, as to limit the spread of raids and such, it is a public server)
And the second is a mute role that takes away their right to participate in all channels on the server. This is a fairly nice feature, because kicking people for minor offenses is fairly dumb, muting them for a couple of hours is far more effective.
But recently, Discord has changed this.
Now since the member role grants permission to read channels, then that overwrites the mute role's statement for those channels. Despite that the mute role is higher on the hierarchy.
I personally were hoping that Discord were going to extend the granularity and features of roles, so that handling semi large servers would become easier without needing to rely on bots for nearly everything. Apparently not....
Edit:
After researching the subject, it seems Discord has never cared about the hierarchy of roles, a yes is a yes, regardless if a higher role says no... (only exception being the Everyone role.)
-
An easy workaround, if I understand the problem correctly, is to simply add the 'muted' role and remove the 'member' role.
-3 -
And that is currently what I am doing.
Though, gets a bit annoying if they also have additional roles giving them access to other channels as well. (Game specific channels, artist channels, etc.)
Because then I need to plot all that information down after muting them, rather tedious work.And before Discord made the change to how permissions work, I could always just give them the mute role and leave all the other roles untouched, and it all worked perfectly.
So the change to how permissions work is an obvious step in the wrong direction as far as my use of roles is concerned. Though, I am not really alone when it comes to running a server with a member role, and other channel specific roles, while also having a mute role.
3 -
honestly It makes me question why the roles even have a hierarchy in the permission list if it's not gonna matter. That being said; any clue if there is going to be an update that's gonna fix this?
5 -
I can't mute a person when he is spamming he have mute role but can write why ?
3 -
^that happens with me too, i’ve done everything to try prevent this but it still happens.
1 -
I'm new to Discord server management, and trying to figure out how all the roles interact, and what the "final" permissions are for any given channel. I think I found the answer to the OP's problem while finding my own answers.
https://support.discord.com/hc/en-us/articles/206141927-How-is-the-permission-hierarchy-structured-
provides this:
Channel Permissions
Channel permissions start with server permissions as a base. Then, the hierarchy is as follows:
- Apply denies of @everyone on channel
- Apply allows of @everyone on channel
- Sum up all the denies of a member's roles and apply them at once
- Sum up all the allows of a member's roles and apply them at once
- Apply denies for a specific member if they exist
- Apply allows for a specific member if they exist
So, to temporarily mute a member just use the Server Settings -> Members screen. Click the stacked dots by the user and select "Mute". When they've learned their lesson, just unselect "Mute". No role needed any longer.
-3 -
(btw sorry for my grammarless english)
uh...
Why (in the case of roles) decide where in the hierarchy is the allows and where the denies cannot be determined by the ROLE height, but by general regulations "because yes" ;-;
this would be helpful for any type of server, both community serwers, looking for players and RP.
Not only for giving a mute, but also for quickly limiting access to a server fragment, which is useful and can be used in many ways - not only as an administrative tool - but also as a self-role switching between server parts.
But I'm not a developer - you probably have your reasons - so as a user that no one bothers with, I'll just say - ok.0 -
There is a solution
Put it so that "everyone" can't read text channels and see voice channels but send message should be put on neutral
The member role should be able to read the channels but send message should also be put on neutral
This makes it so that you need the member role to see the channels. You should still be able to talk as member
Mute role on the other hand should be able to read text channels but should not be able to send messages
4 -
Yeah, that's what I'm doing, Mega Bored, but that's clunky!
1
Yorum yazmak için lütfen oturum açın.
Yorumlar
9 yorum