Separate chat by context
Workspace, office and project sources keep channels aligned with the team structure.
Keep direct messages, project channels, office groups, workspace conversations and shared attachments in ArchiMesh instead of scattering decisions across external chat tools.
The shared chat code explicitly handles workspace, office and project message sources, including direct messages, group channels, attachments and unread state.
The floating chat panel loads channel lists, opens active conversations, sends messages, uploads attachments and updates read receipt state.
Channels are grouped by source so users can distinguish direct, workspace, office and project conversations.
The composer supports attachments and maps uploads to the correct workspace, office or project storage scope.
A WebSocket subscription updates the active channel while unread counts and read receipts track attention.

Move from channel list to conversation view while retaining source, attachments and unread context.

Workspace, office and project sources keep channels aligned with the team structure.
Attachments are uploaded to the correct storage family for the channel source.
Chat records can include audio and video call events so communication history stays readable.
Team messaging connects with meetings, directories, files and project records.
ArchiMesh connects chat, meetings, files, people and project records in one construction workspace.
Start Free Trial