--- schema_version: "1" id: 213665eeceab303bc37976a5284ef61037065bc634c3213096a151dc153e5c5b title: Considerations for Classic Approval Processes in Chatter collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/approvals_for_chatter_considerations.md canonical_url: https://help.salesforce.com/s/articleView?id=platform.approvals_for_chatter_considerations.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 35166c0d7f9bdd3be4968a2266374f78ba6332c318c796cfdf7e0fcf9f0c876c description: Find out more about Approvals in Chatter, before you enable it. products: - Flow Builder - Salesforce Platform release: "264" --- # Considerations for Classic Approval Processes in Chatter Find out more about Approvals in Chatter, before you enable it. ### Required Editions
Available in: both Salesforce Classic and Lightning Experience
Available in: Enterprise, Performance, Unlimited, and Developer Editions
![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_important.png) Important Try [Flow Approval Processes](https://help.salesforce.com/s/articleView?id=platform.automate_automated_approvals.htm&release=264.0.0&type=5 "As your company grows, so does the complexity of your approvals, often requiring input from multiple people in different departments across different time zones. This complexity can mean that you spend more time waiting for each person to complete their review in the right order. Flow Approval Processes helps you coordinate multistep reviews that involve users, systems, and conditional paths."), 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. - When you enable Approvals in Chatter in your org, it’s turned on for all users. Users can then update their own Chatter settings to opt out of receiving approval requests as posts in their Chatter feeds. - Chatter post approval notifications are available only for classic approval processes associated with an object that has been enabled for feed tracking. - If the approval object is a detail object in a master-detail relationship, Owner isn’t available for approval page layouts or approval post templates. ## Limitations - Approvals in Chatter doesn't support delegated approvers or queues. - You can’t recall or reassign an approval request from a post. Instead, perform these actions from the approval record. - Approval requests from Sites or portal users aren’t supported. ## Approval Posts - Approval posts can't be deleted in the Salesforce user interface; you can only delete them through the API. - If you don’t select an approval post template, the approval post uses the system default template or the default template for the object, if available. - Only users with access to the approval record can see the approval request post. Comments on approval posts aren’t persisted to the approval record. - Different users see different configurations of the approval request post. - Only approvers see approval action buttons on their posts, and then only in their profile feed or their news feed. - Only approvers see approver names in the header. - If you change the approver, step name, or the routing type on a classic approval process while it’s in progress, existing approval posts aren’t updated. - When an approval request is recalled, a new post is generated. It appears on the news feeds of the submitter, all approvers, and followers of the object. It also appears on the record feed. - If a step requires unanimous approval from multiple approvers, the approval request post for that step doesn’t list all selected approvers in its header. Approvers see only their own name in the post header. #### See Also - [Let Users Respond to Approval Requests from Classic Approval Processes by Email](https://help.salesforce.com/s/articleView?id=platform.approvals_email_parent.htm&release=264.0.0&type=5 "If the email notification includes all the information that an approver needs to make a decision, enable email approval response. That way, a user can simply reply to the email notification.") - [Prepare to Enable Classic Approval Processes in Chatter](https://help.salesforce.com/s/articleView?id=platform.approvals_for_chatter_getstart.htm&release=264.0.0&type=5 "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.") - [Where Do Approval Request Posts for Classic Approval Processes Appear?](https://help.salesforce.com/s/articleView?id=platform.approvals_for_chatter_overview.htm&release=264.0.0&type=5 "When your org has Approvals in Chatter enabled, approval request posts appear in various Chatter feeds. To see the approval request post, you must have access to the approval record.") - [Limits and Considerations for Classic Approval Processes](https://help.salesforce.com/s/articleView?id=platform.approvals_considerations.htm&release=264.0.0&type=5 "Before you automate something with a classic approval process, be aware of the limits and considerations.")