Separate Dangerous Permissions (E.g. from Manage Channels, Manage Roles, Manage Server)
A huge problem with Manage Roles & Manage Channels is that there is no control over how a user can manage a role or channel.
Say I want to give staff members the ability to change permissions on channels, for example, to temporarily prevent spam, but I don't want said staff members to be able to just wipe the whole server of its chat history and ruin it.
It's impossible to utilize the Manage Channels and Manage Roles permissions when the power the permission gives is attached to the power to ruin a server.
This request here does a good job at giving reasons as to why this is an issue:
https://support.discord.com/hc/en-us/community/posts/360043476072-A-Separate-Permission-to-delete-channels
However, I find the request not general enough. Time and time again I want to introduce new things into my Discord server but I run into the problem of permissions being too intertwined. How can I allow anything to my staff members without the fear that one of my staff member's accounts will be compromised and my entire server with years of history is just wiped?
My only option is to rely on bots, and bots such as Dyno and Auttaja I find to be poorly made and buggy, so, I must use my own custom bots. But, my problem is that I then need to find appropriate hosts for my bots, and, I have none.
Dangerous permissions that can destroy a server should be completely separated, or Administrator-only. The more staff with dangerous permissions, the more risk my server can get destroyed in a moments notice.
Role creation/deletion/permissions, channel/category creation/deletion/permissions, etc should be completely separate from eachother. Additionally, for channel permissions, there should be control for them under categories too. There should be an ability to only have these permissions for certain categories from staff members & users.
This would both solve the danger/risk issue of providing these permissions to staff, and open up new uses for categories, such as custom channels for Patreon members.
-
Even after doing this, since they can manage permissions, they can tick the manage channels, and then delete the channel, it's a loophole, but I think Discord never reads feedbacks anyway.
1
Please sign in to leave a comment.
Comments
1 comment