On Discord, server administrators often need to let members see that a channel exists without allowing them to read any past messages. This is useful for announcement channels, rules channels, or welcome channels where you want members to know the channel is there but only view the most recent post or a specific pinned message. The default permission system ties the ability to see a channel with the ability to read its message history, but you can separate these two actions using a specific permission override. This article explains the exact settings to configure so users can see a channel in the server list but cannot scroll through its message history.
Key Takeaways: How to Hide Message History While Showing the Channel
- Server Settings > Roles > @everyone > Permissions > View Channels: Enable this to allow the role to see the channel in the server list.
- Server Settings > Roles > @everyone > Permissions > Read Message History: Disable this to prevent the role from seeing any messages sent before the current moment.
- Channel-specific permission overrides: Apply the same two settings at the channel level to fine-tune which roles can see the channel without reading its history.
Understanding the View Channels and Read Message History Permissions
To configure a channel so members can see it but cannot read its message history, you need to understand two separate Discord permissions. The View Channels permission controls whether a role or user can see the channel in the server channel list. Without this permission, the channel is completely invisible. The Read Message History permission controls whether a role or user can scroll up and read messages that were sent before they joined the channel or before the permission was applied. By default, enabling View Channels also allows reading message history because the two permissions are often bundled in the UI, but they are technically independent.
When you disable Read Message History for a role, members with that role will still see the channel in the list. They can click on it and see any new messages that arrive after the permission change takes effect. However, they cannot scroll up to view older messages. This setup is ideal for channels that contain sensitive information or for announcement channels where you only want members to see the most recent post. The key is to apply the override at the channel level rather than at the server-wide role level, because server-wide role settings affect all channels equally.
What Happens When You Disable Read Message History
When a member with the Read Message History permission disabled opens the channel, the message area appears empty except for any messages that arrive after the permission change. The member cannot use the search function to find older messages. Pinned messages remain visible because pinning a message is a separate permission. If you want to prevent pinned messages from being seen, you must also disable the Use External Emoji and Add Reactions permissions, but those are not required for the basic setup described here. The member can still send messages in the channel if the Send Messages permission is enabled.
Steps to Configure View Channels Without Read Message History
Follow these steps to set up a channel that is visible but hides its message history. You must have the Manage Server permission or be the server owner to make these changes.
- Open Server Settings
Right-click your server name in the left sidebar and select Server Settings. Alternatively, click the down arrow next to the server name and choose Server Settings from the menu. - Navigate to Roles
In the left sidebar of Server Settings, click Roles. You will see a list of all roles on your server. - Select the Role to Configure
Click the role you want to modify. For example, click @everyone to apply the setting to all members, or click a custom role like Members or Guests. If you want only a specific group to see the channel without history, create a new role first by clicking the + button next to Roles. - Enable View Channels Permission
In the Permissions tab for the selected role, scroll down to the General Permissions section. Toggle the View Channels permission to the green checkmark (enabled). This allows the role to see all channels that do not have a conflicting override. - Disable Read Message History Permission
Still in the same Permissions list, scroll to the Text Permissions section. Find Read Message History and toggle it to the red X (disabled). This prevents the role from reading any messages sent before the permission change. - Save Changes for the Role
Click the Save Changes button at the bottom of the Permissions page. The role now has View Channels enabled and Read Message History disabled at the server level. This applies to all channels that inherit the role’s permissions. - Open the Target Channel Settings
Go back to your server and right-click the specific channel you want to configure. Select Edit Channel from the context menu. - Add a Permission Override for the Role
In the channel settings, click the Permissions tab on the left. Under Roles/Members, click the + button and select the role you just configured from the list. This creates a channel-specific override. - Set the Override to Match the Role Settings
In the override dialog, scroll to View Channels and set it to the green checkmark. Scroll to Read Message History and set it to the red X. Click Save Changes. The channel now follows these settings even if other roles have different permissions.
Common Issues and Limitations
Members Still Can Read Old Messages
If members can still see old messages after you disable Read Message History, check that the permission override is applied at the channel level and not just at the server level. Server-level settings can be overridden by channel-level overrides. Also verify that no other role the member has grants Read Message History. Members with the Administrator permission bypass all permission restrictions. Remove the Administrator permission from roles that should not have full access.
Channel Does Not Appear in the List
If the channel is invisible to the role, ensure that View Channels is enabled in the channel override and that the role does not have a conflicting deny override. Also confirm that the channel is not in a category that has its own permission overrides. Category permissions apply to all channels inside the category unless overridden at the channel level.
Users Can Still See Pinned Messages
Pinned messages are controlled by the Read Message History permission in most cases, but they can also appear in the pinned messages list. If you want to hide pinned messages as well, disable the Use External Emoji permission (which affects pinned message display in some clients) or simply avoid pinning messages in the channel. Alternatively, create a separate channel for pinned content with restricted permissions.
New Messages Are Visible but Old Ones Are Not
This is the expected behavior when you disable Read Message History. Members will see messages that arrive after the permission change, but they cannot scroll up to view earlier messages. If you want members to see only a specific message, consider using a bot to post that message and then disable the Send Messages permission for the role so no new messages appear.
| Setting | Enabled (Green Check) | Disabled (Red X) |
|---|---|---|
| View Channels | Channel appears in the server list | Channel is hidden from the role |
| Read Message History | Members can scroll and read all past messages | Members cannot see messages sent before the permission change |
| Send Messages | Members can post new messages in the channel | Members cannot send new messages |
By configuring the View Channels and Read Message History permissions as described, you give members the ability to see a channel without exposing its full conversation history. This setup is commonly used for rules channels, announcement channels, and welcome channels where you want to control what information is visible at a glance. Remember to test the configuration with an alternate account or by using the View Server as Role feature in Server Settings to confirm the behavior matches your intent.