Source
Encryption & access control — found from sitemap — Rocket.Chat
Checked for Rocket.Chat on 5 Oct 2026
- Page
- https://docs.rocket.chat/docs/configure-e2e-encryption
- Checked
- 5 Oct 2026, 04:41 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:021331ae32f11f24e85a682b9b33d009cef93fad653f06fa2973d984e4374df5
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
E2ee scope Report an error
“Rocket.Chat supports E2EE for private rooms (opens in new tab) and direct messages.”
-
E2ee search limitation Report an error
“Encrypted messages do not appear in search results.”
-
E2ee audit limitation Report an error
“Encrypted content cannot be audited or monitored.”
-
E2ee bots limitation Report an error
“Bots may be unable to access encrypted messages unless they explicitly support E2EE.”
-
E2ee force private rooms version Report an error
“When Force end-to-end encryption on private rooms is enabled (available from Rocket.Chat 8.8.0)”
-
E2ee force private rooms effect Report an error
“every private channel, private team, and private discussion created from that point on is encrypted. The room creator cannot turn encryption off, and the server rejects any attempt to create an unencrypted private room, whether from the app or through the API. Public rooms are not affected.”
-
E2ee federation exemption Report an error
“Federated rooms are exempt, because federation does not support end-to-end encryption.”
-
E2ee force discussions limitation Report an error
“Creating a discussion under an unencrypted private parent room fails.”
-
Version lifecycle Report an error
“Rocket.Chat versions receive support for six months after release. End-of-life for any version is the last day of the month when support ends.”
2 facts read from this page are not shown because they could not be confirmed on the page as captured.