Ask an executive where the company’s chat history lives and you will get a cloud-shaped answer where a location is needed. Retention is the discipline of knowing where content persists, for how long, and under whose command it disappears. The concepts below apply generically across modern platforms, which is exactly why they deserve a page before an audit does.
Where the content actually lives
Channel posts, documents, and call recordings live in different storage areas behind one interface. That split matters: your calendar invite and your spreadsheet behave differently under erasure. A policy is a rule about each kind of content; a bulk rule is a blunt tool and an unreachable rule is a letter of intent.
- Policies set defaults by service and location — the everyday machinery.
- Labels attach a rule to a specific document wherever it travels — the scalpel.
- Holds freeze content regardless of the other two — the legal override.
Practical tip
“Delete” is an instruction to remove, not an erasure spell. Policies may preserve an item for a further period even after a user sinks it — a feature that saves incidents, and surprises people who thought the paper trail died with the message.
Ask the regulatory questions of your own setting
Three questions turn a compliance abstraction into configuration work. What must be kept, and for how long? What must be erased quickly, and on whose word? Who may order an erasure when the normal path is blocked? Map each of the three to a named location in your console — a rule that cannot point at its own setting is a wish, not a policy.
Companies with a working answer can be quick to fix an expired record and slow to panic at a legal request. Companies without one get neither luxury. The rules you define on quiet days are the rules that answer for you on loud ones.
