Discord Channel Deny Permission Not Working

Is this your situation?

The short answer

What you see, and why

Check these first

• Check for a member-specific allow on the channel.Verify: Allows for a specific member are applied last if they exist.
• Check whether the channel is synced to its category.Verify: A synced channel has permissions that completely match that of the category.
• Check the role denies applied to the member.Verify: All the denies of a member's roles are summed up and applied at once after the @everyone allows.
• Check the @everyone settings on the channel itself.Verify: Denies of @everyone on the channel are applied first.

How Discord handles this

• An individual's server-wide permissions are determined by adding up all the allows for roles assigned to that individual along with the allows for @everyone.
• Channel permissions start with server permissions as a base.
• In the channel permission hierarchy, denies of @everyone on the channel are applied first.
• A not-synced channel does not share the same permissions as the category and will not automatically update when the category's permissions are changed.

Which path applies to you?

1. Does the member have a specific allow set on the channel? Allows for a specific member are applied last, which can override an earlier deny.
2. Is the channel synced to its category? A not-synced channel has permissions that differ from the permissions set for the category.
3. Does the member have a role that grants an allow after the deny you set? All the allows of a member's roles are summed up and applied after role denies.
4. Is the deny set on @everyone rather than the role? Denies of @everyone on the channel are applied first.

Step by step: finding the cause

1. Open the channel's permission settings. Permissions of specific text and voice channels can be adjusted through the channel settings menu by hovering over a channel and clicking the cog icon.Confirm: Check the Permissions tab for the roles and members listed.
2. Check whether the channel is synced to its category. A synced channel has permissions that completely match that of the category.Confirm: Check the Permissions tab for a sync indicator or a Sync Now button.
3. Review the @everyone row on this channel. Denies of @everyone on the channel are applied first.Confirm: Check the @everyone row for a deny on the relevant permission.
4. Review each role the member holds. All the denies of a member's roles are summed up and applied at once after the @everyone allows.Confirm: Check each listed role's permission rows on the channel.
5. Review the role allows on this channel. All the allows of a member's roles are summed up and applied at once after the role denies.Confirm: Check for a role allow that could offset the deny you found.
6. Check for a member-level deny. Denies for a specific member are applied if they exist, after the role-level allows.Confirm: Check the Permissions tab's member list for an individual entry.
7. Check for a member-level allow added last. Allows for a specific member are applied last if they exist.Confirm: Check whether the member's name appears with an allow on the channel.

Common mistakes

• Assuming a role deny always wins. A member-level allow applied last can override an earlier role deny.Why it happens: Allows for a specific member are applied last if they exist.
• Assuming all channels in a category share the same permissions. A not-synced channel's permissions differ from the category and will not update with it.Why it happens: A not-synced channel has permissions that differ from the permissions set for the category.
• Overlooking the @everyone deny order. A deny on @everyone is applied before role and member settings, not after.Why it happens: Denies of @everyone on the channel are applied first.

Quick reference

Keeping track of who has access