You are here:
Considerations for Classic Approval Processes in Slack
Find out more about Approvals in Slack, before you enable it.
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.
Users must have the Salesforce Digital HQ app in Slack. When you enable Approvals in Slack in your org, it’s turned on for all users. Before you use Approvals in Slack, make sure you understand the limitations.
- You can connect the Salesforce Digital HQ app to only one Salesforce org.
- The only available actions are Approve and Reject.
- The Show More link doesn’t work for Salesforce Classic users.
- If the approver has to manually select the next approver, they must log in to the full Salesforce site to complete the approval request.
- Users can respond only to approval requests without comments.
- Up to four fields only of an approval request can appear in a Slack notification.
Did this article solve your issue?
Let us know so we can improve!
