March 17, 2025
A clear approval process keeps good decisions moving. It gives every request a defined path and a named approver. It also records who signed off and when. In plain terms, a Salesforce approval process is an automated workflow. It routes a record, such as a discount or a contract, to the right people. They give a yes or no before the deal moves forward.
Most teams start with approvals because manual sign-off gets messy fast. Emails get missed, and records change while a decision is pending. Worse, no one can prove who approved what. A well-built Salesforce Approval Process fixes that. It locks the record during review and notifies the right approver. Then it writes each decision to an audit trail you can trust. Designing that flow well is a core part of any solid Salesforce consulting engagement.
This guide walks you through the full setup, step by step. You will see how to plan the process, assign approvers, and configure actions. You will also test it safely in a sandbox. Later sections show how approvals fit with Flow in 2026. You will learn when to reach for Advanced Approvals and the limits to plan around. A short FAQ answers the questions teams ask most.
A Salesforce approval process is a native automation that reviews a record and routes it for approval or rejection based on rules you set. It works on standard objects like Opportunities, Cases, and Leads, and on custom objects too. You decide what enters the process, who approves it, and what happens at each stage.
Three parts do most of the work. Entry criteria decide which records enter the process. Approval steps decide who reviews the record and in what order. Actions decide what the system does on submission, approval, and rejection. That can mean locking a record, updating a field, or sending an email. Get those three right and the rest is detail. Community walkthroughs like this one on Forcetalks are handy for seeing each part in context.
You reach for an approval process when a decision needs a human yes or no with a paper trail. Discount requests, budget sign-off, travel, vendor contracts, and new-hire offers all fit the pattern. Each one has a clear owner, a clear rule, and a clear outcome, which is exactly what this tool handles well.
Salesforce builds an approval process in a fixed order. The seven steps below match the setup wizard, so you can follow along in your own org. Plan first, build in the middle, and test before you go live.
Start on paper. List the records that need approval and the rule that triggers it. Name who submits the request and who approves it, whether that is a user, a queue, or the record owner’s manager. Decide the number of levels and what happens on approval or rejection. A short plan here saves hours of rework later.
Next, decide how records enter the process. Users can submit a request by hand from the record. An automation can also submit it for them. In Setup, open Process Automation, then Approval Processes. Choose New Approval Process and pick the object. Select the Jump Start Wizard for a quick build or the Standard Wizard for full control. Enter a name, set the entry criteria, and choose manual or automated submission.
Now assign your approvers. Salesforce gives you several ways to route a request. The right one depends on your team. You can send every request to one user or route it to the owner’s manager. You can also share it with a queue or pick the approver from a field. Set delegation so work keeps moving when someone is out. Then test the routing with sample records. Admin tutorials on SFDC Stop show each routing type with screenshots if you want a visual reference.
Initial submission actions run the moment a record enters the process. This is where you protect the record and tell people what is happening. A common setup locks the record so no one edits it mid-review, sends an email alert to the approver, and updates a status field. Add each action under Initial Submission Actions, set the recipients, and write a clear message.
Approval steps set the order of review. A simple process has one step; a layered one has several. Add a step for each level and set the criteria that sends a record there. Then name the approver. You can run steps in sequence, where one approver follows another. You can also run them in parallel, where several approve at once. Add escalation so a late approval does not stall the whole chain.
Now decide what happens at the end. Final approval actions might reopen the record for edits, set the status to Approved, email the submitter, and kick off the next automation. Final rejection actions usually set the status to Rejected, notify the submitter, and create a follow-up task. Map both paths so every outcome is handled and logged.
Test before you launch. Activate the process in a sandbox and submit sample records. Confirm the entry criteria fire, the right approver gets the alert, each step moves as designed, and the actions run. Check the Approval History list to trace each decision. Only roll it out to the whole org once the test run is clean.
A short example makes the parts click. Say your sales team can offer a discount up to ten percent on their own. Anything higher needs a manager. You set the entry criteria to discount greater than ten percent. The record locks on submission, and the manager gets an email. The status reads Pending. If the manager approves, the status flips to Approved and the record reopens. If not, it returns to the rep with a reason. One rule, one approver, a full trail. The same pattern scales to regulated, high-volume decisions, as in our work on fixing slow loan approvals in Salesforce.
The approver you choose shapes how fast and how fairly requests move. The table below compares the four common routing choices so you can match each one to the right scenario.
How you assign approvers is only half the picture. How the request travels through your org is the other half. Salesforce approvals now sit next to Flow, and the two work best together.
Here is the naming shift to plan around. Workflow Rules and Process Builder are retiring. Salesforce now points teams to Flow for record-triggered automation. The approval process itself is still fully supported and is not going away. What changes is the automation around it. Instead of a workflow rule submitting a record, a record-triggered Flow does the job. For multi-stage sign-off across teams, Flow Orchestration adds work steps and stages on top of the classic approval engine.
For most teams the split is simple. Use the standard approval process for the review and the decision. Use Flow to submit records, prepare data, and handle what happens after a decision. This pairing keeps your logic in one modern tool while the approval engine does what it does best. A clean Salesforce integration between the two is where a strong build pays off. Step-by-step guides on Salesforce Tutorial are a good primer on record-triggered Flow basics.
Some deals outgrow the standard tool. Long quote approvals, tiered discounts, and rules that change by product are hard to model with steps alone. That is where advanced routing and the packaged option come in.
Advanced Approvals Salesforce teams turn to is a managed package built for Revenue Cloud and quoting. It adds approval chains and rules by field value. It also brings one-click email approvals and smart resubmission when a quote changes. If your approvals live on quotes and change often, the package saves heavy custom work. For everything else, the native process with Flow usually covers the need. The table below lays out when each option fits.
Even a well-built process has edges to respect. Knowing them up front keeps your design clean.
You cannot add steps to an active approval process. To change the step structure, you clone the process, edit the copy, and activate that. Plan the steps carefully before launch so you clone less often. A record also enters only one approval process at a time on a given object. So keep entry criteria tight and non-overlapping. Watch your order of automation too. A record-triggered Flow and an approval action can both fire on the same save. Build in a sandbox, test each path, and document the design for the next admin. Certification-focused walkthroughs on SaaSGuru are useful when you are training a new admin on these rules.
A workflow, now built as Flow, runs automatic actions when a record meets a rule. An approval process adds a human decision, a locked record, and a routed request with a yes or no at each step.
No. On a given object, a record runs through one active approval process at a time. You can have many processes on the object. Entry criteria decide which one a record enters, so keep those criteria from overlapping.
You cannot edit the steps of an active process. Clone it, change the copy, and activate the clone. Small items like email templates can change without a clone, but step structure needs the copy-and-activate path.
Parallel approvals send one request to several approvers at the same time. You choose whether the record needs every approver to agree or just the first response, which is useful when finance and legal review the same deal together.
No. The standard process is fully point and click. You add code or a managed package only for advanced patterns, like quote-based approvals or routing that a formula cannot express on its own.
A dependable approval process is engineering, not just configuration. The clicks are easy. The hard part is designing entry criteria, routing, and the automation around them. Done well, the whole system stays clean as your org grows. That is the difference between a process that holds up for years and one that gets cloned into a mess. This is the discipline our team brings to every build.
Minuscule Technologies designs Salesforce approvals as part of a governed automation architecture. Flow, integrations, and testing are built in from day one. Our Accelerators and Starter Packs give you tested approval patterns, naming standards, and deployment guardrails. You launch faster and on a foundation that scales. We are a trusted Salesforce engineering partner, and approval design is one place that engineering depth shows.
Ready to build approvals your team can rely on? Book a free call with our Salesforce team, and we will map an approval design around how your business actually makes decisions. Bring your trickiest sign-off scenario, and we will show you the cleanest way to build it.
You've seen what's possible. Now, let's make it happen for your business. Whether you need an end-to-end Salesforce solution, a complex integration, or ongoing managed services, our team is ready to deliver.
Schedule a Free Strategic Call
Plot No. 4, Sridevi Amman Street, Perumal Nagar Extension, Old Pallavaram, Chennai, Tamil Nadu 600117, India.
