Glossary · Platform

Managed channel

A managed channel is a room whose contents the server can read, which is what allows server-side search, retention rules, audit trails and organisation-wide export to operate on it.

Open betaThe platform is being built in the open, so parts of it are not there yet, behaviour changes between releases, and no availability figure is committed while it is in beta. What is still being built.

What Managed channel means

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.

The capabilities a managed room buys are the ones organisations discover they need slowly and then need urgently: finding a decision made eighteen months ago, deleting a category of message on a schedule, producing a defensible record when somebody asks for one, and taking the whole archive elsewhere. None of these is possible over ciphertext.

The cost is equally concrete. A managed room is readable by anybody who can compel or compromise the operator, and the protection it offers is organisational and legal rather than mathematical. A conversation whose confidentiality must not depend on the operator does not belong in one.

How Enclessa uses it

Enclessa channels are managed rooms. Search runs server-side over message bodies and text extracted from uploaded files, retention rules apply, and the organisation export includes them. Enclessa does not describe channels as end-to-end encrypted anywhere, because they are 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.

Related terms

Room modeA room mode is the fixed property of a conversation that decides whether the server can read its contents, chosen when the room is created and never changed afterwards.Read the entry End-to-end encryptionEnd-to-end encryption is a design in which a message is encrypted on the sending device and decrypted only on the receiving devices, so that the server carrying it holds no key that can open it.Read the entry Retention policyA retention policy is a rule stating how long a category of data is kept before it is deleted, applied automatically rather than left to somebody remembering.Read the entry Audit logAn audit log is an append-only record of who did what, to which object, and when — kept separately from application logs so that it can be relied on as evidence rather than read as debugging output.Read the entry Compliance exportA compliance export is a bulk extraction of message and file records in a structured format that a supervision, archiving or e-discovery system can ingest, rather than one a person is expected to read.Read the entry Tenant isolationTenant isolation is the guarantee that no request made by one customer organisation can read or change any data belonging to another, enforced by the system rather than by convention.Read the entry

Read further

The security page explains how Enclessa protects data and which certifications it does not hold. The trust centre covers the processing agreement, the subprocessors and the residency position. The FAQ answers the questions buyers ask most often.

Encrypted collaboration, hosted in Europe.

Create a workspace in a couple of minutes. It is yours at your-team.enclessa.app, hosted in the European Union, with encrypted direct messages from the first one you send.

Create your workspace See pricing

Open beta. Free plan, no payment card to start.