Separate manage channel permissions please :)

This feature request is similar to this post,

What is the Problem?

Right now there is only a single permission: Manage Channels, for users to edit channels, meaning they can:

• Edit a channels name, description, and voice/text settings
• Delete the channel
• Edit categories 

Separating this permission into sub permissions is what I think needs to happen. This would be especially helpful for discord servers with complicated setups, and several roles whom they may want to give limited permissions to like creating custom voice channels.

Because the Manage Channels permission is so powerful, I highly advise everyone to disable this and configure them by category/channel. If you don't, they'll have an over-powerful ability to delete channels/categories and/or edit them. In both cases, either of giving them this permission, or not giving them this permission as a role, you'd be forced to disable it per channel/category. This creates some inconsistences and problems.

How do roles/permissions work?

For people who don't understand Discord's permission and hierarchical structure: Disabling a permission for @everyone, either as a role or channel/category, takes place for every user no matter what other roles they have. Meaning, a role or channel needs to explicitly set that permission to (✓), even if a user acquires a role that is of higher priority and the permission is set to (/). In addition, this means disabling a channel permission for a role but enabling it for @everyone will affectively do nothing and still enables that permission for the user. Why? Because the user is still counted towards as @everyone. This relation takes place between any roles and any number of roles.

Example:

Let's say you have a discord with 3 roles: @everyone, @member, and @staff. You created a channel called #staff and gave admins the ability to see the channel by setting their View Channel permission to true (✓). A user joins your discord and you give them both member and admin. As long as you have the admin role above member, they will be able to see the channel. If you were to switch the priority of the two ranks, the user would no longer be able to see the channel. If on the other hand, you left the admin's permission for viewing that channel as default (/), the member would not be able to view the staff channel. If on the other other hand, you set everyone's permission for viewing that channel as true (✓), then the disabling of any roles above it would literally do nothing. And all users can see the channel.


Recommendation:

When you're setting up your discord, I recommend setting up permissions first through the roles. And leaving the channel/category permissions of @everyone mostly blank, unless needed to change. This way, there's less to set up and you can avoid the madness I described above. Example:

I set up the roles how I wanted and want a channel only viewable for a special role called "Alpha"

Setting @everyone to View Channel (X)

Setting Alpha to View Channel (✓)

Done. That's it. Leave everything else blank to give Alpha the ability to talk, etc. 

X= Disallow permission
/ = Defaults to role permission
✓ = Allow permission

So I did some testing:

Firstly, in both cases of having Manage Channels enabled or disabled, and meanwhile of having @everyone as default (/) or (X), giving Manage Channel or Manage Permission a (✓) created huge problems. The user had full ability to edit @everyone or their own's channel/category permissions, among some other things, it was hierarchical madness. Setting @everyone to (X) and Manage Channel to (/) just disabled the ability entirely because as stated before, it applies to everyone. So you really are forced to give them (✓). 

How I've dealt with the problem

The absolute best setup I found to somewhat give admins or staff the ability to create channels, to not edit their own or @everyone permissions in a category, and to not delete specific channels in that category is as follows:

1. Set the role permission of Manage Channels to false
2. Set the role permission of Manage Roles to true
3. Go to a category where you want this structure to take place
4. Give @everyone the default (/) permission for all permissions in that category
5. Give the admin role a (✓) for Manage Channels 
6. Sync all channels to that category
7. Any channels you do not want them to delete: set Manage Channels to (X), I also recommend you setting Manage Permissions to (X) as they will be able to sync the channel to the category and thus be able to delete. (example of why separation should be a thing)

Picture of what your channel/category should look like from admin's perspective.

Now they can create channels, such as a voice channel, and only edit non-powerful permissions in those channels and the category as a whole! Yay!

How can we solve this?

So as stated before, this isn't a huge issue, but could definitely be improved upon by separating these permissions into sub permissions. I'm happy to explain this in more detail to anyone/any mods, or assist in anyway to achieve this.

Examples of how things could be further separated:

• Deleting a channel
• Deleting a category
• Creating a channel
• Creating a category

Quick Tip

Quick Tip before I go: Do you want a Muted role to work in private channels such as a donator lounge, limiting Muted users from talking but still allowing them to view the channel, whilst @everyone cannot? Here's how:

1. Make sure your role permissions are set up properly.
2. Set @everyone to View Channel X, and leave the rest as default (/).
3. Set the @donator role to View Channel (✓), leave the rest as default (/), or customize normally.
4. Create a muted role with no permissions.
5. Go to the channel where you are setting this up.
6. Set the @muted role Send Messages to (X) and Read Message History to default (/)
   
   Like I said in my post, if you wanted donators to not send emojis for example, you could disable it for @everyone, but touching @everyone is dangerous. I recommend only touching it to disable View Channel and leave everything else as default to allow for further channel customization and quick setup.