Mattermost Threads: Setup, Usage, and Team Adoption

Mattermost threads, also called Collapsed Reply Threads (CRT), are replies that live in a sidebar instead of cluttering your channel. This guide shows you how to enable them, use them, and get your team to actually adopt them so your channels stay readable.

What Are Collapsed Reply Threads in Mattermost?

Mattermost threads are replies that appear in a sidebar instead of inline in the main channel. When you reply to a message, it creates a thread. Everyone in the channel can see there is a thread, but the individual replies stay out of the way unless they click to read them. This keeps channels clean and readable, especially when dozens of conversations are happening in parallel.

The core idea is simple: one original message, many replies. You can have a support ticket discussion, a project debate, or an incident response all happening in the same channel without the channel feed becoming a wall of text. Each thread sits in the sidebar on the right side of your screen, and you can read it without losing your place in the channel.

This matters because busy channels become unreadable without threads. Try managing a 50-person team chat where every message is top-level and you will be drowning in noise. Threads let you have focused side-conversations while keeping the main channel for announcements and decisions. Not every message needs to be seen by everyone; threads let you opt in to what you care about.

Threads also prevent one person from dominating a channel with a single line of reasoning. A debate that would normally fill a channel history with 30 messages instead becomes one message with 30 threaded replies. Your channel history stays clean for future team members reading it.

Enabling Collapsed Reply Threads: System Admin Setup

Mattermost provides four configuration modes for threads, managed by your System Administrator. These are: Off (no threads), Default Off (threads exist but are off by default), Default On (threads are on by default), and Always On (users cannot turn threads off). Most teams choose Default On or Always On to encourage adoption.

To enable threads as a System Administrator, go to System Console, then Feature Flags, and search for "Collapsed Reply Threads". You will see the current setting and four options:

• Off: Threads do not work. No user can create or view threads. Use this only if you are certain your team will not need them.
• Default Off: Threads are available, but users start with threads disabled. Users must manually opt in to see threads in the sidebar.
• Default On: Threads are enabled for all users by default. Users can still turn threads off in their settings if they prefer.
• Always On: Threads are on and users cannot disable them. The sidebar always shows threads.

Most teams starting out should choose Default On. It turns threads on for everyone but allows users who strongly prefer the old flat style to opt out. Enforcement can come later once the team sees the benefit. When you change this setting, it applies immediately to all users without requiring a server restart.

Here is what this means for your ops role: a team that knows about threads but forgets to turn them on will blame the tool, not themselves. You need to make a conscious business decision: are threads mandatory for this team, or optional? If you are managing a support team or incident response group, set them to Always On. If you are managing an engineering team that already has a different discussion system, start with Default On and monitor adoption.

How to Reply to Messages and Create Threads

Creating a thread is the same as replying to a message. On web or desktop, hover over any message and click the Reply icon (looks like a reply arrow). This opens a sidebar panel where you type your response. Mattermost automatically threads your reply to that message. No special action needed; the message you are replying to becomes the thread root.

On mobile (iOS or Android), long-press a message and tap Reply. The thread sidebar appears at the bottom of the screen. Type your response and send. Mobile threads work identically to web, but the UI adapts for smaller screens. Important caveat: a bug was reported in July 2026 on Mattermost Mobile version 2.42.1 where threaded replies became invisible. If you see this, update your Mattermost server to the latest patch version. Mattermost pushes mobile fixes regularly, and rendering issues are usually resolved in the next release.

When you reply to a message, visual cues tell you that a thread exists. Under the original message, a small indicator shows how many replies are in the thread. If your server has Collapsed Reply Threads enabled, threads will not show inline in the channel; they only appear in the right sidebar or in the dedicated Threads view.

Once someone replies to a message, that message becomes a thread root and you cannot turn it off. Anyone in the channel can see there is a thread, and clicking on the message opens the thread. This is why threads are powerful: they are visible but optional. Your team sees signals of conversation without being forced to read every word.

Following, Unfollowing, and Managing Thread Subscriptions

When you reply to a message, follow a thread, or are mentioned in a thread, Mattermost automatically adds you to that thread. You are now following the thread, which means you will get notifications when new replies arrive (depending on your notification rules). Automatic following prevents you from missing replies to conversations you started or participated in.

To manually follow a thread you have not replied to, click the thread to open it and look for a Follow or Watch button in the thread header. Click it and you are now subscribed. This is useful when you want to watch someone else's conversation without adding your own reply. To unfollow, click the same button (it will now say Unfollow).

Unread indicators tell you when a thread has new replies you have not seen. A blue dot appears next to the thread message or thread name in the sidebar. When you read all replies in a thread, the blue dot disappears. You can also manually mark a thread as read by right-clicking the thread and selecting "Mark as read" on web and desktop; mobile has a slightly different menu. Undo this with "Mark as unread".

Managing thread subscriptions is how you keep your notification load sane. If you are following 30 threads and every one has 10 new replies, you will be buried. Mattermost is good about only notifying you when someone mentions you or when you actively replied. But if you want to aggressively manage your load, unfollow threads you have watched but do not need to stay on top of. You can always re-follow later.

The Threads View: Your Thread Inbox

The Threads view is a dedicated panel in Mattermost that shows all threads you are following, sorted by most recent. On web or desktop, click the three-dot menu in the sidebar and select Threads, or look for a Threads label in your sidebar (toggle it on in your client settings if it is not visible). This opens a vertical panel listing every thread you follow, with the newest at the top.

From the Threads view, you can click any thread to read it and jump to that conversation. If the thread is in a channel you are not actively viewing, Mattermost switches you there. You can see the number of unread replies in each thread (shown as a blue badge). You can also mark all threads as read with one click, which is useful for batch catchup at the start of your workday.

The Threads view is where you triage. Many teams have a practice of checking their Threads view first thing in the morning: scan for high-priority threads, read mentions, and mark the rest as read. This is much faster than trying to skim every channel you are a member of.

On mobile, access the Threads view from the main menu (hamburger icon). Tap Threads and you see the same list. Mobile rendering is narrower and scrollable, but the functionality is identical to web.

Understanding Thread Notifications

Thread notifications follow different rules than channel message notifications. By default, when someone replies in a thread you are following, you do NOT get a notification unless you are mentioned or the thread has specific notification settings. This is intentional; it prevents notification fatigue.

Here is the notification matrix for threads:

• Someone replies to your thread (you started it): You get a notification. Mattermost assumes if you started a thread, you want to know when people respond.
• Someone mentions you in a thread (@yourname): You get a notification. Same as a channel mention.
• Someone replies to a thread you manually followed: Depends on your settings. By default, you do NOT get notified; you have to check the Threads view. If you want notifications for a specific thread, right-click the thread and set the notification preference to All Activity or Mentions.
• Muted threads: If you mute a thread, you will not get notifications from that thread even if you are mentioned. Muted threads are different from muted channels.

For your team, this is the key gotcha: some team members will feel they are missing important thread replies because they are not getting notifications. The truth is, thread notifications are off by default unless you are the thread starter or mentioned. If your team wants to be notified of all thread activity, they need to change their notification settings per thread. Alternatively, you can set a server-wide default in the admin console, but that will flood inboxes.

Best Practices for Team Communication

The fundamental rule: thread replies to messages and post announcements to the channel. Do not post your follow-up thought as a new top-level message if it is a reply to someone else. Make it a thread. If it is new information that everyone should see immediately, post it to the channel.

For teams new to threads, set a few norms:

1. Support tickets and customer conversations: Always thread. Each customer message gets its own thread so your team can have a full conversation without spamming the channel.
2. Project debates and decisions: Thread. When someone suggests an approach or raises a problem, the discussion belongs in a thread. Once you reach a decision, post the decision as a top-level message so everyone sees the outcome.
3. Incident response: Do not thread during an active incident. Post top-level to the channel so the incident commander can see the latest status quickly. Once resolved, thread the post-mortem discussion.
4. Questions and how-tos: Thread. If someone asks "how do I deploy this?", reply in a thread so future team members reading the history do not see 20 messages of back-and-forth.
5. Announcements, policy changes, celebrations: Always post to the channel. Never hide announcements in threads.

Adoption takes about two weeks. Your team will resist at first ("threads slow me down" or "I do not want to click to read"). The resistance fades once they see two benefits: (a) they can check the thread inbox without scrolling through a hundred messages, and (b) quiet team members start speaking up because threads feel safer than spamming a channel.

To encourage adoption, send an email when you enable threads, showing a short 2-minute demo video. Then be consistent: if someone posts a reply as a top-level message when it should be threaded, reply with "Hey, this reply belongs in a thread to [original message]." After a few gentle nudges, the behavior sticks.

If you are running Opsily's managed Mattermost hosting, your instance comes configured for threads. Our ops team handles the server configuration and upgrades, so you do not debug mobile rendering bugs or manage feature flags yourself. You focus on team adoption while we handle infrastructure.

Troubleshooting & Gotchas

Mobile rendering issues: Mattermost Mobile 2.42.1 had a bug where threaded replies became invisible. If you see threads missing on mobile, check your Mattermost server version. Update to the latest patch (Mattermost releases mobile fixes regularly). If you are on the latest version and threads are still broken, clear the mobile app cache (Settings > Apps > Mattermost > Clear Cache) and restart the app.

Threads not appearing in sidebar: Your team might have toggled threads off in their client settings. Tell them to go to Account Settings > Display > Threads and make sure Collapsed Reply Threads is set to On. If this is a server-wide issue, check System Console > Feature Flags and confirm Collapsed Reply Threads is not set to Off.

Notification overload: If your team is getting too many thread notifications, the issue is usually a server-wide setting that notifies on all thread replies. Go to System Console > Notification > Send notifications on thread replies and set it to Do not send. Let your team control notifications per thread. This solves the problem without breaking workflow.

API access for developers: Mattermost has endpoints to fetch thread data (GET /api/v4/posts/{post_id}/thread). Developers can use this to build integrations or report on thread activity. Full API docs are at the Mattermost API reference. If you want to export thread data for compliance or analytics, you will need custom tooling or a third-party integration.

Performance at scale: If your team is running hundreds of active threads, thread lookups can slow. This is rare in teams under 500 people, but it happens. The fix is usually database index optimization (Mattermost admins can tune this) or a server upgrade. If you manage a very large Mattermost deployment, managed Mattermost hosting handles infrastructure scaling for you.

Threads in archived channels: If you archive a channel, all threads in that channel are archived too. You can still read them, but you cannot add new replies. This is intentional (Mattermost prevents conversation in archived channels).

Frequently Asked Questions

How do I know if someone has replied to a thread I care about? If you started the thread or replied to it, Mattermost sends you a notification. If you manually followed the thread, you do not get a notification by default; check the Threads view. To get notifications for a specific thread, right-click and set the notification preference.

Can I move a conversation from the channel into a thread after the fact? No, Mattermost does not have a move feature. If a conversation has already spread across the channel, you have to manually copy replies into a new thread. This is why enforcing threading from the start matters.

What happens to threads when the original message is deleted? The thread disappears. If someone deletes a message, the entire thread is removed. This is a hard rule in Mattermost. If you want to keep thread history, do not delete messages.

Do threads appear in Mattermost search results? Yes. When you search for a keyword, Mattermost returns matches from both channel messages and thread replies. You will see the thread parent and the matching reply listed separately in results.

Can I use Mattermost Copilot to summarize threads? Yes, if your Mattermost instance has Copilot enabled and an LLM configured. Copilot can read a thread and generate a summary or key points. This is a premium feature requiring additional setup. Not all teams have it.

Are threads synced across multiple Mattermost instances if I run a cluster? If you run a Mattermost cluster (multiple servers for high availability), threads are stored in the shared database and synced automatically. No additional configuration needed.

What if my team just does not want to use threads? You can set threads to Off in the System Console, but try them for two weeks first. Most resistance fades once teams see the benefit. If your team genuinely prefers flat channels, threads are optional in most configurations.

The Bottom Line

Mattermost threads turn a cluttered channel into an organized inbox. Enable them, show your team a 2-minute demo, and enforce gentle norms: replies go in threads, announcements stay in the channel. Adoption takes two weeks, and after that, your team stops complaining about channel noise.

The gotcha to watch is mobile. Check recent Mattermost release notes if your team reports threads missing on phones. The lever you control is the System Admin setting: Default On works well for most teams. Always On is better for enforcing adoption in structured teams (support, incident response).

If you are running Mattermost yourself, threads are free but require configuration and monitoring. If you want infrastructure that just works, Opsily's managed Mattermost hosting handles setup, upgrades, and scaling so you focus on team adoption.