Platform
Managed channel, explained
The word "managed" is doing precise work here. It does not mean unencrypted — content is encrypted in transit and at rest — it means that the operator holds a key, and therefore that capabilities requiring the content to be legible are available. That distinction is invisible in most product copy, which is exactly why it deserves its own term.
How Enclessa uses it
Enclessa channels are managed rooms by default; an end-to-end encrypted channel exists only where an organisation permits it and somebody chooses it at creation. In a managed channel, search runs server-side over message bodies and text extracted from uploaded files, retention rules apply, and the organisation export includes them. Enclessa never describes a managed channel as end-to-end encrypted, because it is not. The platform control plane Enclessa operators use still cannot read them: it is a separate identity restricted to metadata, and a build check forbids it from importing any code that could read content.