Let Users Respond to Classic Approval Process Requests from Chatter
If your users don’t need in-depth information to decide how to respond to an approval
request, enable Approvals in Chatter. That way, they don’t have to leave their feed to continue
with their day-to-day tasks.
Required Editions
Available in: both Salesforce Classic and Lightning Experience
Available in: Enterprise, Performance, Unlimited, and
Developer Editions
Important Try Flow
Approval Processes, a modern alternative to Classic Approval Processes. This new
feature provides a more flexible, user-friendly flow-based interface, and it can trigger on
record changes, supporting Apex extensibility and detailed logging for compliance and audit
trails. It supports dynamic routing based on data and business rules, unlike Classic Approval
Processes, which are tied to specific objects and offer limited support for processes by using
conditions. With Flow Approval Processes, you can monitor submitted records and quickly
identify bottlenecks, giving you unprecedented visibility into approval workflows. And, like
Classic Approval Processes, Flow Approval Processes don’t consume automation credits or
orchestration runs.
Prepare to Enable Classic Approval Processes in Chatter Because Approvals in Chatter relies on both Chatter and the Classic Approval Processes feature, getting your org set up involves more than just turning on the feature. Before you enable Approvals in Chatter, understand the limitations and considerations for Approvals in Chatter and post templates.
Enable Classic Approval Processes in Chatter If your organization has both Approvals and Chatter enabled, administrators can turn on Approvals in Chatter. Users then receive approval requests as posts in their Chatter feeds.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.