Chatter is available in sites built using Aura and Salesforce Tabs + Visualforce templates. While many features that support customer and partner site are available only in Aura sites, some features are available in both types of templates.
Required Editions
| Available in: Salesforce Classic and Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions |
| Applies to: Aura and Visualforce sites |
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.
- Add Rich Publisher Apps to Your Feeds
Customize the Chatter publisher with payloads that are unique to your business process. Add a form to a post; choose from a selection of branding images; add inspiration to your feed with profound quotations. Select from the custom apps your team creates or acquires from AppExchange. Add up to five apps to the Chatter publisher. - Enable Chatter Questions in Your Experience Cloud Site
Chatter Questions helps you promote engagement by giving users the ability to ask and answer questions in their Chatter feed, in groups, and in records. Members in your users’ groups and Experience Cloud sites can answer questions in Chatter just as they would comment on a Chatter post. Users in sites built on the Customer Service template can also attach files to questions. - Data Model for Peer-to-Peer Conversations in Experience Cloud Sites
Experience Cloud uses Chatter behind the scenes for peer-to-peer conversations in Experience Cloud sites. To keep conversations in your internal org separate from the ones in an external-facing site, each Chatter post or conversation is tied to the Experience Cloud site that it belongs to. If you have more than one external-facing site, the same is true for conversations in each site—each one is tied to the site that it belongs to.