@everyone can view channels
The member starts with View Channel from the server-level @everyone role. Their other server roles are added to that base.
DISCORD CHANNEL PERMISSIONS GUIDE
Resolve channel access in the order Discord actually uses.
A member's channel access starts with server roles, then passes through @everyone, combined role, and individual overwrites. Work through the sequence once and a mysterious private room usually becomes a traceable configuration result.
✓Eight-stage resolution order✓Category sync explained✓Member exceptions disclosed
THE RESOLUTION ORDER
Calculate one member, one channel, one permission at a time
Choose a concrete question such as “Can this member view #staff?” and track only View Channel through the sequence. Repeat for Send Messages, Connect, or any other permission after the first result is clear.
Start with @everyone at server level
Apply the server-wide permissions on the guild's @everyone role.
Add every assigned role
Combine the server-wide allows from all roles assigned to the member.
Stop for Administrator
If the combined base includes Administrator, Discord grants all permissions and bypasses channel overwrites.
Apply the channel's @everyone overwrite
Apply its denies first and its allows second.
Combine all matching role denies
Collect the denied flags from every channel overwrite targeting one of the member's roles, then remove them.
Combine all matching role allows
Collect the allowed flags from all matching role overwrites, then add them. This is why a role allow can beat another role's deny.
Apply a member-specific deny
If the channel has an overwrite for the individual member, apply its denied flags.
Apply a member-specific allow
Apply that individual overwrite's allowed flags last.
This order follows Discord's current Permissions reference. Role position is not a tiebreaker during the combined role-overwrite stages.
WORKED EXAMPLE
Why a second role can reopen a denied channel
@Muted denies; @Support allows
The channel has a View Channel deny for @Muted and an allow for @Support. The member holds both roles.
The member can view the channel
Discord combines role denies and then role allows, so the @Support allow restores View Channel. Moving @Muted higher will not change that calculation.
If the intended policy is that muted members must never see the room, a conflicting role allow makes the role design unsuitable for that policy. Test the actual multi-role member rather than relying on the label or role order.
RELATED RULES
The final bitfield is not the whole user experience
View and Send gate other actions
Denying View Channel makes other channel permissions unusable. Denying Send Messages also makes actions such as attachments, embeds, TTS, and mentioning everyone unusable even if their flags remain present.
Synced is a state, not permanent inheritance
A synced child channel mirrors its category's overwrites and follows later category changes. Editing the child's permissions desyncs it, so later category changes no longer propagate.
Parent visibility still matters
Threads use the parent channel's permissions. A member needs View Channel to see its threads and Send Messages in Threads—not ordinary Send Messages—to write inside them.
MANUAL DEBUGGING
A repeatable check in the Discord client
- Write down the affected member, channel, and exact missing or unexpected capability.
- List @everyone plus every role assigned to that member. Check for Administrator first.
- Open the category and determine whether the channel is synced or has its own overwrites.
- Inspect the channel's @everyone overwrite, then every matching role overwrite.
- Inspect an overwrite that targets the member directly; it is evaluated after role overwrites.
- Check whether View Channel, Send Messages, or Connect makes another flag unusable implicitly.
- Use View Server As Role from an owner or Administrator account, then test the real member when multi-role or individual exceptions matter.
Change one layer at a time and preview the result before applying it broadly. Duplicating an overwrite across category, channel, and individual levels makes future audits harder even when the immediate result appears correct.
PRODUCT BOUNDARY
What DisplayState resolves automatically
Role-level perspectives across channels
DisplayState reads supported guild permissions and role-targeted channel overwrites, identifies Administrator bypass, and groups channels with the same effective result. Invalid or unresolved permission values stay visible as limitations.
Real member combinations and exceptions
The current audit does not inventory who holds which roles, combine every member's assigned roles, or apply member-specific overwrites to a role perspective. It does not read messages or silently rewrite channel access.
For the other layers, read the role hierarchy guide, review @everyone permissions, or see the full permission audit.
STRAIGHT ANSWERS
Frequently asked questions
Do channel permissions override server permissions in Discord?
Channel overwrites modify the server-level permission result for that channel. Administrator is the exception: it grants all permissions and bypasses channel overwrites.
Does Deny always beat Allow in Discord channel permissions?
Not as a universal rule. Within the combined role-overwrite stage, Discord applies all matching role denies and then all matching role allows. A member-specific overwrite is evaluated afterward, with its allow applied after its deny.
What does a slash mean in Discord channel permissions?
The neutral slash means the channel has no explicit allow or deny for that role or member on that permission. Discord continues with the permissions produced by the other applicable server and channel rules.
Does DisplayState inspect member-specific channel overwrites?
DisplayState records that member-specific overwrites exist but deliberately does not attribute them to its role-only perspectives. It also does not inventory member role combinations, so individual exceptions still require manual review.
FREE DURING BETA
Turn channel sprawl into a reviewable access map.
Run a private Discord configuration audit, inspect supported role perspectives, and keep unresolved coverage explicit.
Audit channel permissions