The question arrives in every onboarding queue, usually anonymously: can my employer read this? The workplace answer is less dramatic and more useful than either “yes, everything” or “no, it’s private”. Visibility is a design, not a mood — and most designs can be learned in ten minutes.
Routinely visible
Some things an administrator sees as a matter of course:
- Usage signals — that you signed in, from which device, roughly when. Attendance at a machine level, no content.
- Metadata of collaboration — that a conversation grew long, which files were opened, which workspace got busy. Patterns without words.
- Membership and documents — who is in which room, and what was posted to it. If the room is visible, its posts are visible. A private channel changes the audience, not the rule.
Worth knowing
A work conversation inside a work tool is the employer’s record almost everywhere — that is what a work tool is. Personal matters therefore belong in a personal channel: a private email account, a personal phone, never the office platform. The boundary is not surveillance paranoia; it is simply separation of documents from conversations, applied in the right direction.
Deliberately visible
A second tier requires action, and is therefore the honest boundary the first tier offers: search across the whole record during an investigation, a compliance export, a legal hold, or a direct look at a specific conversation where a real safeguarding concern exists. Each action leaves a trace on the platform — and the trace is a better protection than the promise.
Employees can work with the design, too. The company handbook answers the standing policy; the specific questions belong to the IT team, not to guessing. Ask the exact question — “under what conditions can someone read my messages?” — and the answer stops being a rumour.
