Create Accountor Login
Docs

Threads and Team Mentions

Part of the MountDev Ops Channels documentation. Updated November 16, 2026

MountDev Ops Channels documentation | Updated November 16, 2026

Our Commitment

MountDev Ops is built security first. Your business data belongs to you, and you can export all of it at any time. We never use analytics or tracking of any kind inside MountDev Ops.

Every update passes all 4,888 automated checks before it ships, and every screen change is walked through before release.

What a Thread Is

A thread is the replies to one message in your team's own chat. Reply in a thread and the answer stays next to the message it answers, and only the people in the thread are told. Everyone else in the channel is not pinged, and the channel does not fill up with side talk.

Threads work in team channels, direct messages, and the chat on every project, task, and ticket. They never work in a website visitor's chat or a text: a customer always sees one plain line, and nothing in a thread is shown to a customer.

Reply in a Thread

Every message in a team conversation has Reply in Thread under it, always visible, including messages that were written before threads existed. Select it and the thread opens inside the Chat window, sliding over the conversation, with the original message pinned at the top, the replies below it in order, and the reply box at the bottom (action channels.thread.reply).

  • A reply stays in its thread, always. There is no box or setting to also send it to the channel. If something matters to everyone, write it as a normal message in the conversation.
  • Threads are one level deep. A reply to a reply goes in the same thread, so nobody gets lost.
  • Replies take files, reactions, and @mentions like any message. A file is shared the same way as in a conversation and is kept with the conversation, so whoever may read the conversation may open it.
  • An archived channel's threads can still be read, but they take no new replies.
  • Nothing is deleted. Replies stay with the conversation, and a reply from someone who left the team keeps their name.

Under a message that has replies you see 3 replies, the initials of the last people who replied (up to three, newest first, with a plus count when more people took part), and the time of the last reply. Select it to open the thread. A message with no replies shows no line.

Back (the arrow, or Esc) slides the conversation back and puts you where you were. Esc a second time closes the Chat window. Opening a thread (action channels.thread.open) reads it for you, and its notices on the bell.

Who Is Told

You are in a thread when you wrote the original message, replied in it, were mentioned in it, or followed it. A reply tells only those people on the bell ("Mia Member replied in a thread in #general"), never the person who wrote it, and never someone who muted the thread. Someone who is not in the thread gets no notice, no unread count, and no dot, but can open the thread from the message and follow it.

A reply never changes a conversation's unread count or its dot, and it never counts as a must-read post.

Everyone is checked against the conversation's own rules: someone who cannot read a private channel cannot open its threads, is not told about them, and stops seeing them the moment they are taken out of the channel. Nothing is deleted when they are.

Follow, Unfollow, and Mute Thread

The thread's menu, in its header, has these (action channels.thread.follow):

  • Follow Thread adds you, and what is already there counts as read.
  • Unfollow Thread takes you out. You can open it again from the message.
  • Mute Thread turns its notices off for you only. It still shows in your Threads view, without a dot. Unmute Thread turns them back on.

The Threads View

The Chat tab has a switch, Conversations | Threads, with the number of unread threads on Threads, and that number is added to the Chat tab's count. Threads lists every thread you started, replied to, were mentioned in, or follow, newest activity first, 30 at a time (action channels.threads.list). Each row shows the first line of the original message, the conversation ("#general", or the other person's name for a direct message), why it is yours ("You started it", "You replied", "You were mentioned", or "Following"), the number of replies, the time of the last one, and a dot when something in it is new.

All and Unread filter the list. Mark All Read clears every thread dot at once (action channels.threads.read_all) and never changes a conversation's own unread count. It shows only threads in conversations you may read right now.

Tagging a Team

Type @ in the message box of a conversation or a thread, and the list shows people and teams in one list, 8 at a time. A team shows a people icon, its name, Team, and how many people are in it ("Installs Team | 4 people"). Pick a team and it is tagged. A team is a Group on the Staff page (Groups), and it includes every team inside it.

  • Typing a team's name by hand without picking it from the list sends plain text and tells no one.
  • The tag tells each member of the team once, on the bell ("Mia Member mentioned Installs Team in #general"), but only people who can read the conversation. Someone who cannot read it is not told, and you are not shown who they were. After sending you see counts only, such as "Installs Team mentioned. Told 3 people. 1 person in this team cannot read this conversation, so was not told."
  • You are never told by your own tag, and a person who muted the thread is not told. A person in two tagged teams, or tagged by name as well, gets one notice.
  • In a thread, a team tag brings its members who can read the conversation into the thread as mentioned.
  • A team of more than 500 people is told in batches in the background, so sending answers at once.
  • The tag shows in the message as the team's name. If the team is renamed later, older messages show its new name. If the team is removed, its name stays as plain text and nobody is told.
  • Both ways of tagging, in a conversation (action channels.send) and in a thread (action channels.thread.reply), work the same. The list is action channels.people.

Making a Team Taggable

A team can be tagged only where an owner or admin allowed it. On the Staff page, Groups tab, Add a Group and Change have Can Be Mentioned, off at first (action core.groups.save). Every Group that already exists starts off, so nothing starts telling anyone. When it is on, Who Can Mention It is one of:

  • Anyone who can post: every person who can write in the conversation.
  • Only its leaders, owners, and admins: the people in the team's Led By list, and the leaders of any team it sits inside, plus owners and admins. A team with no leader yet means owners and admins only, and the screen says so.

Turning it off takes the team out of every list at once and deletes nothing. Earlier tags stay as plain names. If someone tries to tag a team that is off, or that only its leaders may tag, they see one plain sentence ("Installs Team cannot be mentioned." or "Only the leaders, owners, and admins of Operations Team can mention it.") and nothing is sent. Every change is in the Activity Log.

The Chat Assistant

Your chat assistant (The Chat Assistant) can be asked inside a thread with @. It is sent that thread and nothing else of the channel, and it answers in the same thread. It may tag a team only when the team is on and set to Anyone who can post.

AI Agents

A connected AI agent or API key never opens, reads, replies in, lists, or follows a thread, or changes a Group's mention setting: team chat is between people, and Groups stay with people. The actions are channels.thread.open, channels.thread.reply, channels.threads.list, channels.thread.follow, and channels.threads.read_all.

Your Data

Threads are kept in your company's own database with the conversation, nothing is deleted, and Export Everything (Exporting) includes them: the Messages sheet has a column, In Reply To, with the number of the message a reply answers.

Ask Us Anything

We’d love to hear from you!