Channels, threads & search
How this is scored
The daily surface: channel model, threading, mentions, files, and whether search can find a decision made eighteen months ago.
0 — Not a team chat: no persistent channels or group conversations, only notifications or one-off messages.
3 — Group chats or channels and direct messages, file sharing, and search over messages.
5 — Public and private channels, threaded replies, mentions and reactions, file sharing with previews, and search across message history.
8 — Cross-organisation or guest channels with clear boundaries, message editing history, pinned and saved items, search with filters by channel, person and date, and unlimited history or a documented history limit per plan.
10 — The archive is a working knowledge base: search that ranks well across years, threads that stay readable, channel lifecycle management (archive, rename, merge) without losing history, and export of a conversation in a form a human can read.
The Security Officer
Threads, reactions, attachments and search are documented — search even inside encrypted rooms — with unlimited history stated outright, so a decision from eighteen months ago is still there and findable. Spaces build enterprise-wide room hierarchies that can be shared externally, but I found no public information on message edit history, pinned and saved items, filtered search by channel, person and date, or channel lifecycle management, which is what would make the archive a working knowledge base. 2 5 6