Team Chat mark unread — put a conversation back in your unread list
You read a message, then need to come back to it. Alt+click it — or open its action menu (the right-click menu, or the ⋯ button) and choose Mark unread. That conversation's read position moves to just before the message you picked, so it and everything after it show as unread: the badge returns in the sidebar and the conversation comes back to your attention list. The position is stored in your own read state, so your other computers and the web app show the same badge.
On this page
How to do it
- Alt+click any message in a channel, a direct message, or an open thread. A short "Marked unread" note confirms it happened. Alt+clicking a link, button, reaction or the message editor does nothing — those keep their own click behaviour.
- Right-click the message (or use its ⋯ button on a narrow window, which opens the same actions as a sheet) and choose Mark unread, the same way you would mark an email unread.
- Right-click a conversation in the sidebar — a channel or a direct message — and choose Mark unread. That puts the conversation back to unread from its newest message, so the badge returns without you having to open it and hunt for the message. (Once it is unread, that same menu offers Mark as read to clear it again — see Team Chat mark as read.)
- It works on your own messages too, so you can flag a message you sent as something to come back to.
What it does to your read position
- Your read position for that conversation becomes one millisecond before the message you picked. Every message from that one onward counts as unread; everything before it stays read.
- The unread number shown on the conversation is the count of messages from that point on that other people wrote — at least one, so a conversation never looks silently caught-up.
- The rule that keeps a badge from moving forward is deliberately not used here: marking unread is the one action allowed to move your position backward.
It stays unread while you stay in the conversation
Marking unread while a conversation is open does not get cleared a moment later by the normal "you are looking at it, so it is read" behaviour. It behaves like Slack: the badge stays while you remain in that conversation, and the moment you leave it and come back, ordinary read tracking resumes — so opening it again reads it. The divider showing where your unread messages start sits at the message you marked, so it is waiting for you when you return.
A direct message gets exactly the same treatment. A DM conversation is normally cleared for you as soon as you have it open in the front window — that is what keeps the DM list quiet — but that automatic clear stops for the conversation you just marked unread, so a DM goes back to unread and stays that way.
Choosing Mark as read for that DM is how you hand it back to the ordinary rule. The badge clears at once, and the protection lifts as soon as that read position has actually been written — a few seconds later, when the undo window closes. From then on a message that arrives while you are sitting in the conversation clears itself the moment you are looking at it, the same as any other conversation. Pressing Undo inside that window puts the badge back and keeps the protection with it, so the DM stays unread until you leave it and come back.
A channel you marked unread behaves the same way and is handed back the same way: right-click it in the sidebar and choose Mark as read — see Team Chat mark as read for what that does.
Across your devices
The new position is written to your own read document in the workspace, the same document every Omniscio computer and the web app read — including a computer that already has the app open, which takes the earlier position the moment the change reaches it. Mark a conversation unread on your desktop and the badge is there on your laptop. Nothing about the position is shared with anyone else — it is your own read state, readable only by you.
If the save cannot reach the server (offline, or the write is refused), the badge is put straight back to where it was and you are told it did not work, rather than being left with an unread badge no other device agrees with.
One case that looks surprising
A thread reply does not move the conversation's own newest-message time, so if you mark unread from a reply that is newer than any top-level message, the unread state starts at the newest top-level message instead. The reply itself lives in its thread, and opening the thread still has its own reply indicator.
What it does not change
- It never deletes or edits a message, and it changes nothing for other members: only your own read position moves.
- It does not touch a conversation's notification settings. If a conversation is muted, it stays muted; marking it unread brings the badge back, not the alerts.
- One case a badge cannot show: if the newest message in the conversation is one you typed, the badge stays quiet by design (a message you wrote is not evidence somebody is waiting for you), even though the position itself did move.
Last verified 2026-11-20