"Override lower roles" setting for permissions
Currently, if a user has any role that sets a permission to positive, then they have that permission, regardless of higher roles that set the same permission to negative. This is clearly impractical, and leads to the issue that it is impossible to mute a user in a restricted channel. In servers where all users have a role that allows them general access, and by default new users cannot chat until they are given this role, it becomes impossible to mute anyone, server-wide, as no matter the hierarchy of the mute role, their lower role allows them to chat.
A simple solution is a tickbox next to permissions for a role, that says "override lower roles?". This would then ignore settings for any lower roles for that permission, and a user would receive the permission of the highest role that overrides those below it, or, if there are none, then as normal.
-
2 years later it's still a problem! FFS! Can't you just make our life easier Discord? You gave us the abbility to for example give our YT sponsors a role that's called Youtube Member. If I want to mute anyone with this role I CAN'T! It's impossible! I can't take this role away from them, becouse it's been given by discord. Having 100+ sponsors on one server with them having more provilages than the regular viewers is a pain in the ass. If you can't give us a good working role hierarchy then just give us a working mute button! Currently the only option is to kick/ban a bad behaving user or make having a "Youtube Member" role useless. I just can't wrap my mind around it. FIX IT!
1 -
UPVOTED!
1 -
Why did they change it in the first place?
This is simply restrictive.0 -
Discord, just confirm that whether you're working on this issue, we would be happy to wait, if you're working on this.
Thank you.
3 -
Come on Discord, this is a pretty essential feature for people to be able to properly manage their discords.
2 -
This issue is still not fixed? Come on Discord, we want to be able to mute members on our Discord-Servers with the use of bots.
0 -
This is still a problem. I would like it to be like this:
- More than 1 role can be combined to get access to a channel.
- Make it so that a role can deny a permission too, and not just allow.
1 -
why is this still a problem 2 years later
1 -
I keep coming back to this thread cause I swear this issue is gonna give me a nervous breakdown. Role Hierarchy is very much needed. I just need my muted role to work in restricted channels without having to remove every other role first
2 -
I have found a workaround.
I enable general stuff for everyone execpt view channel
Then i add roles that can view specific channel.
Then just add denies to that role if they shouldnt be able to do that and keep the perm available to this role on gray tick0 -
Example
Everyone:
cant view channel
Can send mes
Can manage mes
Gen Role:
Can view channel
Cant manage mes
Higher role:
Can view channel0 -
Well, in my opinion we can make this post upvoted a lot, I mean when we get 10000 votes, discord might consider us. Let's try, ask your friends to upvote and we'll make it happen, (maybe?)
1 -
This is a non issue as far as I understand it.
The issue seems to be people do not want to give everyone full access until they have a certain role, but then when they have that role wish to mute them later.
There are two very simple solutions to this.
First - there is the bot approach - use a bot that will remove the troublesome role that is green in permission. That is very simple to do on Yag and even Carl bot has a hard mute option to remove roles.
Then there is the fancier way I do things which takes more time to set up. But I will explain it to you cos it is far more convenient to execute.
I have mute, media mute, video mute and jail roles. I have private moderator, group and gender chats. But everyone in my server can see everything. And read everything. So how do I do this?
On join, everyone gets roles for what they cannot see. Automatically. When they become moderators, the role blocking the mod room is lifted off them. Nothing is positively affirmed. It is all neutral or denied. No green at all. On join noone can see NSFW, but instead of reacting to get an NSFW role, the role preventing NSFW is REMOVED from them.
So what about Male and Female? On join they are blocked from both. On the roles reaction menu, simply set one bot to give the female or male role on reaction. On the very same emoij on the same post, set another bot to REMOVE the autojoin role that was preventing access. One click - role restricting access removed and new role for tagging given. Voila :) Some bots may do one that one thing on a reaction, but it easy enough to have Yag and Carl working together on the same reaction emoji.
If someone wants to join private cricket, clubhouse, gaming categories, the role restricting them is lifted. And they can get the new tag role for that community.
The advantages of this are, if you want to mute someone, you just role them mute, if you want to jail them (cannot read anything but jail channel) you simply jail role them. They can retain all other roles.I can literally jail a mod. And they goto jail and cannot see the mod room. I and moderators do not need to remove any roles to remove someone's media or video privileges.
This works also if you want to set up new joins to goto the rules room only, and read the rules, then when they emoji react - you remove the role blocking the entire rest of the server.
It is simply doing everything upside down and ignoring green permissions. I just dont use them. Only neutral and red.
Like I say - it takes a bit more time to set up, but its really easy if you sync the cat permissions right first time. Yes you need to set up numerous auto join roles, but that's a breeze on bots like carl and yag and pro bot (oh yeah - I have double redundancy).
Yes it is more time consuming to set up. But its so much easier to moderate once it is set up. Because everyone has everything. You never need to worry about removing roles. You just give them the blocking role. Then unblock them later.-9 -
My Red Kite
That's not the actual issue. The issue is that if someone has a lower role enabling access of a chat (Which I assume would be a role that, say, allows people to understand who've read the rules, and therefore should not be removed) and a higher role that prohibits access of that chat, they'll still see that chat.
The issue is that the "deny" permissions get applied BEFORE the "allow" permissions.
3 -
For me it's the "Server Booster" role that automatically gets applied. I want Server Boosters to see a certain channel but only after they're verified. You can't remove or manage a Server Booster role. So, as a result, Server Boosters can see server booster channels before they're verified because yes overrides no. There's nothing you can do about that.
The only way I can get around this is to have no permissions assigned to "Server Booster" and to have some role called "Server Booster Verified" that's assigned only to server boosters when they get verified but I'm not sure there's bots that can do that outside of making my own bot.
1 -
I know this doesn't fix the problem, and I wish Discord would fix this. But, I just found something that may help some people - I know it won't fit everyone's needs.
I had this same problem until today. My situation was, I have a role players need to have to post (agreed to terms), a muted role, and an assortment of other rules. Order in hierarchy goes:
- Muted
- Miscellaneous Roles (like 14 of them)
- Agreed-Terms Role
- Everyone
What I had to do was go through every single role in the Server Settings and turn OFF Send Messages. The only roles that stayed on were my Moderators and the Agreed-Terms Role. Then, in Channel/Category Permissions, I set Everyone to Middle/Gray, Agreed-Terms to Middle/Gray, didn't touch the Miscellaneous Roles, and then Muted to Left/Red/Negative.
This made it so all my roles except the approved one can talk, all the others can just see, and no matter what role you have - if you are muted, you can't talk. So the only real change I had to make from what I was trying to do, was ensure the Speak permissions in Server Settings were all off except the one I want to talk.In my particular server I wanted it so people can still read channels, just not post to them. So if you wanted to change reading you would follow the same steps.
I know this likely won't help everyone, but hopefully it helps some of you.
2 -
xBusse
This was a HUGE pain in the ass to do... BUT IT WORKED. Thanks a lot!
1 -
I have like 77 channels that I now have to redo because Discord's higher roles no don't override lower roles yes. Please fix this so others don't have to do the same thing.
Edit: The following configuration is impossible with the current setting
Default: view only
Special role: can type
Muted: negates special
0 -
PeacefulPotato, I confirmed on my server that my setup still works. Not sure if this will help you, but I hope it does.
Role Settings:
Everyone: View Messages - True, Send Messages - FalseMuted: View Messages - True, Send Messages - False
Special Role: View Messages - True, Send Messages - True
Make sure your Muted Role is still above your Special Rule in the order hierarchy
Then, the annoying part... your individual channel/category sections (most of my channels have separate permissions than their category... that was just poor planning on my part)
Everyone: View Messages - Middle (inherit permissions), Send Messages - Middle
Muted: View Messages - Middle, Send Messages - Left (Deny)
Special Roles: View Messages - Middle, Send Messages Middle
This makes it (on my server) so that everyone can see, but no one can send. Once you get the Special Role, they can now see and send everywhere. If they are muted, the mute permission is stripped from them. The reason this works is, the Channel/Category Permissions for my Special Role are not set to "Accept"/"Right"/Green Checkmark. If you have any channels with your Special Role set to "Accept"/"Right"/Green Checkmark, then Discord does not care about Higher Role priority and overrides the Mute.
0 -
Why is this not fixed after years? Discord's permission system is just awful, starting at the fact that if I want people to be able to pin things, I also have to allow them to delete everyone's messages...
But this is just basic stuff. I have a role for advanced activities that allows people access to high tier channels, then I have a hierachry of multiple roles that get writing privileges one by one over time when a new activity opens (core players first, then regulars, then newbies/new members).
I can't even timeout people who misbehave because their roles will always override that permission denial.How is basic stuff like that not implemented after all this time of people asking? Seriously...
1 -
Right now my server has the same exact problem and even if we put the mute role higher then the regular member (verification) role. The member role will override.
0 -
Found this thread while tearing my hair out over this issue. You can make it work BUT it's a huge pain if you have tons of roles because you have to go in and do every single role over and over. Also sucks because if you miss one you won't notice or have any idea where you missed it.
Ridiculous issue I say go with the soft vs hard type of system someone else posted in the first page.
0 -
+1
0 -
Just got into this issue as well!
This whole permission system is sometimes so confusing.
As it was already mentioned before, a higher role with a permission set to no should overwrite lower role permissions where the option is set to yes.0 -
Oh my god, why has this not been fixed yet?! What I've read from these comments is that you have to do it one by one with each role you have, and I have... a lot on my Server. I was hoping to get this to work, but I guess I can't because I don't wanna go through the pain of doing role by role and channel by channel. Please Discord, sort this out.
0 -
Adding in my comments to keep this issue fresh and relevant.
This continues to be a problem for many users and servers.
A large server that I moderate is facing an issue where "Muted" members can send messages in a channel that is read-only for many & read/write for a privileged few--in an environment where membership gating is already in effect with roles.
This is possible because the "Muted" individuals inherit the write permissions from a conceptually "lower" role.It's my understanding that any known workarounds do not apply here and this design continues to be a very relevant problem.
With accessibility and intuitive user experience in mind, this is arguably a bug.Please, we are begging you to fix this.
In the meantime, I suppose we need to get the word out that this issue needs more votes.Thanks for your time.
1 -
FIX THIS.
Two years! Two years, Discord. Just give me a way to hard-mute someone for the love of god. How hard is this? Let me make a role that overrides all other permissions. Or make hierarchy affect access. This is so, so, so basic and so ludicrously simple to fix. There's like half a dozen valid suggestions that would remedy this in this thread alone.
PICK ONE.
2 -
yes pleaseeeee discord
0 -
New ui broke the hirearchy and this needs to be fixed.... DON'T MAKE A TUTORIAL ABOUT IT IF IT DON'T WORK!
IT IS LITERARY RIGHT THERE...
https://support.discord.com/hc/en-us/articles/214836687-Role-Management-1010 -
I still don't understand why Discord staff didn't fix this in 2 years.
The current permission system is very limited due to this behaviour.2
Zaloguj się, aby dodać komentarz.
Komentarze
Komentarze: 133