Approval Process

An Approval Process in Salesforce is an automated series of steps that routes a record to one or more people for approval or rejection before it can proceed (for example, before a discount is applied or a document is finalized). Approval Processes can include multiple steps, conditional routing, and automated actions based on the outcome (approved, rejected, or recalled). Salesforce offers two approaches: Classic Approval Processes (the traditional point-and-click setup) and Flow Approval Processes (a newer, more flexible alternative built into Flow Builder).

PRACTICAL EXAMPLE

A sales rep needs manager sign-off before offering a discount over 20% on an Opportunity. An admin sets up an Approval Process on Opportunity: when the discount exceeds 20%, the record is automatically submitted to the rep’s manager for approval. If approved, a field is updated and the rep can proceed; if rejected, the rep is notified and must revise the discount.

Quick Facts

  • Approval Processes can route to a specific user, the record owner’s manager, a queue, or be dynamically determined based on a field on the record (for example, a “Next Automated Approver” field).

  • Multi-step Approval Processes support different approvers and different criteria at each step, not just a single approve/reject decision. Final approval actions run only after all required approval steps are completed. For example, if a request requires approval from a manager and then a CEO, the final approval actions run only after both approvals are obtained.

  • Submitting a record for approval locks it by default, so only approvers and admins can still edit it while it’s pending. Record Editability Properties determine whether only administrators or administrators and the currently assigned approver can edit the locked record.

  • Approval Processes can trigger Field Updates, Email Alerts, Tasks, Outbound Messages, or run a Flow automatically at each step (initial submission, approval, rejection, or recall).

  • For Classic Approval Processes, Salesforce limits an org to 1,000 active approval processes and 2,000 total approval processes. Each object can have up to 300 active processes and 500 total processes.

  • A single approval process can contain up to 30 approval steps, with up to 25 approvers per step. Community sources report a limit of 30 approval steps per process.

  • Approval History is tracked and viewable on the record, showing who approved or rejected and when.

  • Salesforce allows up to 40 initial submission actions, 40 final approval actions, 40 final rejection actions, and 40 recall actions per approval process.

Warning icon

Note

While a record is locked during an Classic Approval Process, users (including the owner) generally cannot edit it unless they have special permissions or the process is configured to allow edits. This can create workflow friction if approvers are slow to respond, since the submitter often cannot make small corrections without first recalling the approval request.

FAQ

What's the difference between a Classic Approval Process and a Flow Approval Process?

Classic Approval Process is Salesforce's original point-and-click approval tool, tied to specific objects with limited condition-based routing. Flow Approval Process is a newer alternative built into Flow Builder, offering a more flexible interface, the ability to trigger on record changes, Apex extensibility, detailed audit logging, and dynamic routing based on data and business rules. Both are available at no extra automation cost, but Salesforce positions Flow Approval Process as the modern alternative.


What happens to a record while it's pending approval?

The record is locked by default when submitted to a Classic Approval Process. Users with “Modify All Records” for the object or “Modify All Data” can edit the locked record. Record Editability Properties can also allow the assigned approver to edit it.


Who can recall a pending Approval Process request in Salesforce?

In a Classic Approval Process, the original submitter can recall a pending approval request if the admin enables Allow submitters to recall approval requests. If this option isn't enabled, only administrators can recall the request. Recalling the request unlocks the record by default, allowing the submitter to make changes and resubmit it for approval.


What is a dynamic Approval Process in Salesforce?

A dynamic Approval Process routes approval requests based on record data or business rules rather than assigning the same approver to every request. In a Classic Approval Process, automated routing can use a standard or custom hierarchy field, such as Manager, to determine the approver. Flow Approval Processes provide more flexible dynamic routing based on data and business rules.