Learn About Encrypting Chatter Data

Note Beginning in Summer ’26, Chatter is turned off by default in all new orgs. For any features in these orgs that require access to Chatter functionality or the Chatter APIs, turn on Chatter by going to Setup | Chatter Settings and selecting Enable. For details, see Chatter Is Turned Off by Default in New Orgs Beginning in Summer ’26.

Enabling encryption for Chatter automatically encrypts eligible data across various Chatter elements. You can use this feature on its own, or in addition to Database Encryption. When you use Chatter encryption when Database Encryption is on, the Chatter encryption happens first using its own tenant secret.

Encrypted Chatter data includes data in feed posts and comments, questions and answers, link names, and URLs. It also includes poll choices and questions and content from your custom rich publisher apps.

The revision history of encrypted Chatter fields is also encrypted. If you edit or update an encrypted Chatter field, the old information remains encrypted.

Chatter data is stored in the Feed Attachment, Feed Comment, Feed Poll Choice, Feed Post, and Feed Revision objects. The database fields on these objects that house encrypted data is visible from the Encryption Statistics page in Setup.

• ChatterExtensionInstance—Payload
• ChatterExtensionInstance—PayloadVersion
• ChatterExtensionInstance—TextRepresentation
• ChatterExtensionInstance—ThumbnailUrl
• ChatterExtensionInstance—Title
• FeedAttachment—Title
• FeedAttachment—Value
• FeedComment—RawCommentBody
• FeedPollChoice—ChoiceBody
• FeedPost—LinkUrl
• FeedPost—RawBody
• FeedPost—Title
• FeedRevision—RawValue

Enabling Encryption for Chatter encrypts all eligible Chatter fields. You can’t choose to encrypt only some Chatter fields.

Some fields listed in the Encryption Statistics aren’t visible in the UI by the same name. However, they store all encrypted data that’s visible in the UI.