Skip to content
Guide

How to stop threads in read-only Discord channels

To stop members posting in a read-only channel through threads, deny @everyone Create Public Threads, Create Private Threads and Send Messages in Threads on that channel, as well as Send Messages. Turning off Send Messages alone is not enough, because threads have their own permissions.

By Digital DenUpdated November 5, 20265 min read

Why a locked channel still has open threads

Most servers make announcement and rules channels read-only by turning off Send Messages for @everyone. Members can no longer post in the channel, so it looks locked.

Threads are separate. Starting a thread is governed by Create Public Threads, and posting in one by Send Messages in Threads. If @everyone still has those, anyone can open a thread under your announcement and post whatever they like, often where every member is looking.

announcements

Mod Team Yesterday at 6:02 PM

Season 4 starts Friday. Brackets go up tomorrow.

quickcash_77 started a thread: FREE NITRO, claim fast

FREE NITRO, claim fast38 messages

quickcash_77 first 50 to click get it free

You do not have permission to send messages in this channel.
Thread vulnerability#announcements: @everyone can see it and cannot send messages, but can still Create Public Threads.

The four thread permissions

These are the permissions that decide what members can do with threads in a channel, and how to set them on a read-only one.

PermissionFor @everyone
Create Public ThreadsStart a thread anyone who can see the channel can open.Deny
Create Private ThreadsStart an invite-only thread inside the channel.Deny
Send Messages in ThreadsPost in threads, including ones someone else started.Deny
Manage Threads and PostsRename, close, lock and delete threads, and see private ones. A staff permission.Staff only

Fix one channel

  1. 1Open the channel's settings: Edit ChannelPermissions.
  2. 2Under Advanced permissions, select @everyone.
  3. 3Set Send Messages, Send Messages in Threads, Create Public Threads and Create Private Threads to the red cross, which denies them.
  4. 4Save. Members can still read the channel, but cannot post in it or in any new thread.

Want staff to keep using threads?

In the same screen, add your staff role and allow Create Public Threads and Send Messages in Threads for it. A role's allow on the channel beats the deny on @everyone.

Threads members already opened stay where they are. Close or delete any you do not want with a staff account.

Fix a whole category

If your read-only channels share a category, such as an Information category, set the same denies on the category in Edit CategoryPermissions. Channels whose permissions are synced with the category pick them up. A channel with its own overrides is not synced, so check those one by one, or sync them to the category. With EvaluBot Premium, /auditchannels template applies a read-only template to many channels and categories at once, threads and polls included, and asks before it removes a channel's own overrides.

Fix it server-wide

To close the gap in every channel at once, turn off Create Public Threads on the @everyone role in Server SettingsRolesDefault Permissions, which is @everyone. It is one of the permissions Discord gives @everyone by default.

That stops members starting threads anywhere, unless another role or a channel override allows it. If your community uses threads in its chat channels, allow Create Public Threads for @everyone on just those channels.

Check your other roles

@everyone is only the baseline. If a role most members have, like Member or Verified, grants Create Public Threads, those members can still open threads in a channel unless the channel denies it for that role too.

  • Open each member role in Server SettingsRoles and look for Create Public Threads and Create Private Threads.
  • Use View Server As Role on the role to see the channel exactly as its members do.

Forum and media channels

In forum and media channels every post is a thread, so threads are the point. This gap only matters in text and announcement channels, which is where EvaluBot looks for it.

Check every channel at once

Finding the gap by hand means opening every channel's overrides. EvaluBot's thread vulnerability check does it in one audit: it flags every text and announcement channel that @everyone can see but not send messages in, while @everyone can still Create Public Threads.

It judges each channel from what @everyone can actually do there, the role plus the channel's own override, so turning off Create Public Threads on the @everyone role clears it. The gap costs 10 points on the security score until it is closed, and the audit never changes anything itself. See the full security checklist for more settings worth checking.

FAQ

Why can members create threads in my announcement channel?

Because threads have their own permissions. Turning off Send Messages for @everyone stops posts in the channel itself, but if @everyone can still Create Public Threads, anyone can start a thread under it and post there.

Does turning off Send Messages stop threads in Discord?

No. Send Messages only covers the channel itself. Threads use Create Public Threads, Create Private Threads and Send Messages in Threads, so deny those as well.

Can staff still create threads in a read-only channel?

Yes. Deny the thread permissions for @everyone on the channel, then add an override for your staff role that allows Create Public Threads and Send Messages in Threads.

What is a thread-vulnerable channel?

EvaluBot's name for a text or announcement channel that @everyone can see but not send messages in, while @everyone can still Create Public Threads. Every audit flags each one, and the gap costs 10 points until it is closed.

Find every open thread gap.

One /audit checks every text and announcement channel for the thread loophole, and scores the rest of your server too. Read-only from start to finish.

Join the Discord servers already running EvaluBot.

Running a busy server? Premium gives it 15 audits a month, every risky change as an alert, fix plans and more. See Premium