Permissions (Grey Slash)

FirecowTest

I just tried setting up a discord server.

I remove all permissions for @everyone in Server -> Role

Then I created a new channel, all the boxes under permissions had grey slash, but @everyone was still able to see my channel.

What does "grey slash" mean, if it isn't "inherit server permission"?

3

Comments

8 comments

Date Votes
  • $h4døw__Hunt3r

    Thats because the grey slash is neutral
    Which means it is dependent on the persons permissions so if u set some stuff to a red x then they wont be able to see it

    -3
  • $h4døw__Hunt3r

    But yet
    It also depends if that @everyone hav a role or not

    -3
  • FirecowTest
    • Edited

    "Thats because the grey slash is neutral"

    @everyone has a role under Server -> Roles, where all is unchecked, to make sure that everyone can't do anything.

    I thought "grey slash" meant inherit server permissions. Apparently it does not.

    So what does "neutral" mean?

    0
  • $h4døw__Hunt3r

    Neutral means it wither good nor bad
    Like lets say u hav 3 groups
    2 of them hate each other to the core(lets say group A and group B)
    The third group is like a wild card(lets call it group wild)
    If Group A wants to prank Group B then group wild would accept depending on its state and same the other way around
    Group wild is pretty much the neutral side of this story

    Get it now?

    -7
  • Rami Emad

    We understand what the word "Neutral" means! @Shadow_Hunter ... I can't happen to find how the permissions are inherited if the "Slash" is checked! Do they get their Role permissions or do they get the Server's permissions?

    It needs clarification @Discord

    5
  • Firecow
    • Edited

    Yes...
    We need to know, where the system actually finds channel "greyslash" fallback permissions from. @Discord

    0
  • BANDWICHES
    • Edited

    I rewrote my original post based on feedback from Discord support (Edited - 4/20/2020).

    Disclaimer:

    There is no such thing as inheriting permissions when it comes to Discord.  "/" equates to "root" which in this case means "server".  In other words, pull the permission from the server role (not inherit from parent).

    Discord has two basic "levels" of permissions - server and channel.  You may think "what about categories"?  Well, channels don't need categories.

    Well isn't the channel inheriting from the Server (it's parent)?  Yes!  It does do that!  But it's more complicated than that.  The Server is the only parent, period.

    Unfortunately, Discord has chosen to go with their own proprietary system instead of proven and true systems like Active Directory or NTFS when building out their permissions system.

    Permission Options:

    [X] denies permission

    [/] pulls permission from the server

    [Check] permits permission

    Special Role:

    [@everyone] is applied to everyone included users with roles.  It's the base set of permissions that all other roles and permission are applied upon, it will be overridden by literally anything (Role, Category, Channel).

    Special Permission:

    Read Text/View Voice channels - This is a special permission that can affect new users when set at the server level.  New users by default have no roles and so they take on the @everyone server level permissions.  If they are not able to read/view channels at the server level then they will not be able to read/view any channels at all unless explicitly set on the category or channel via the @everyone role.

    Problems:

    Confusion.  It's non-traditional, there's no documentation, there's no layman terms anywhere.  In fact, there is no other popular system today that behaves this way that I can think of.

    Redundancy.  Channels don't inherit from categories so they have to "sync" with the parent in order to "inherit" permissions from the category.

    Sync With Category.  This option only exists because true inheritance does not.  in order to "inherit" permissions from the category, you just set your permissions exactly the same as the category (or click the sync button).  Categories serve a very limited purpose in this system.

    Tree View.  There's no way to view permissions in a tree, in fact having to exit and click between channels and categories makes it even hard to remain on track and increases the likelihood you're gonna jack something up.

    Security Issues.  Because one simple [/] in the wrong spot can throw off your entire server with permissions and without a way to view permissions in a tree-like way, Discord has basically set you up for failure in regards to securely setting up permissions accurately on your first go around (this includes hobbyists and professionals in IT).

    Summary

    [/] always pulls from the server setting no matter if it's set at the Category or Channel.

    Discord permissions are essentially security through obscurity with a tiny hint of actual security.  You have a 99% chance of screwing something up anytime you touch permissions or roles in any way shape or form.  Permissions cannot be inherited, only set at the channel or pulled from the server.  Categories serve a very limited and finite purpose.

    0
  • grapmatie

    I had the same problem and asked the same question to Discord. From them I only got the answer that the meaning of the gray slash is that the server permissions will apply. I also found in my own server that a channel that has been around for some time has an error. It doesn't matter what I set there, but the roles didn't do what I intended. The solution for me was to delete and recreate the channel. The gray slash means again the server permissions will apply.

    I hope this solves also your problem.

    1

Please sign in to leave a comment.