Salesforce Approval Process vs Flow Approval: Architecture, Audit Trail, and Best Practices
Salesforce now offers two very different ways to handle approvals. The classic Approval Process is still the fastest option for simple, record-centric approvals. The newer Flow Approval Process model brings approvals into a Flow-first design, with stages, steps, screen flows, and orchestration-style control. For architects and developers, the key decision is no longer just "can this approve a record?" but "which option gives the right balance of flexibility, auditability, admin maintainability, and enterprise scale?"
1) What is the classic Salesforce Approval Process?
Classic Approval Process is Salesforce's long-standing, declarative approval engine for records. It provides built-in submit, approve, reject, recall, approval history, and related reporting constructs. It is best when the process is predictable, mostly linear, and tightly tied to a single record. Salesforce still documents this model as the legacy or classic approach alongside the newer Flow-based approval model.
Where it works well
- Manager approval on a discount, contract, or quote.
- Simple two-step approval such as Manager → Finance.
- Cases where audit visibility matters more than advanced branching.
- Teams that want minimal custom development.
Built-in capabilities
- Submit for Approval and approval actions.
- Approval history and related reporting model.
- Email actions, reassignments, recalls, and escalations.
- Low-code admin setup for straightforward use cases.
2) What is the Flow Approval Process?
Salesforce's Flow Approval Process is a Flow-first approval model built around a sequence of stages and steps. Steps can run sequentially, concurrently, or based on defined requirements, and each approval step is associated with an active screen flow. This design makes Flow approvals much more adaptable than the classic approval engine, especially when approvals are only one part of a larger business workflow.
Where it works well
- Dynamic approver assignment using data, roles, or business rules.
- Approvals that need custom screen experiences.
- Parallel or conditional review stages.
- Enterprise workflows that include integrations and non-approval actions.
What you typically build
- Record-triggered or launched approval entry point.
- Stage and step logic in Flow Builder.
- Custom status fields and reporting model.
- Optional custom audit object for approval actions.
3) Approval Process vs Flow Approval: side-by-side comparison
| Area | Classic Approval Process | Flow Approval Process |
|---|---|---|
| Setup effort | Low to medium for standard record approvals. | Medium to high depending on UI, routing, and audit design. |
| Approval UI | Built-in approval experience. | Screen-flow-driven and more customizable. |
| Dynamic routing | Limited compared with Flow logic. | Strong support for conditional and data-driven routing. |
| Parallel or advanced branching | Limited. | Much stronger through stages and steps. |
| Audit history | Automatic approval history model. | Needs deliberate design for custom audit and reporting. |
| Integration friendliness | Not ideal for orchestration-heavy processes. | Much better fit for broader workflow automation. |
| Admin maintainability | Generally easier for simpler scenarios. | Can become complex if over-engineered. |
| Best fit | Simple, linear, compliance-friendly approvals. | Complex, multi-stage, enterprise workflows. |
Pros of classic Approval Process
- Fastest way to launch a standard approval flow.
- Strong built-in auditability and familiar related lists.
- Good fit for straightforward business controls.
- Less custom design work for admins and support teams.
Cons of classic Approval Process
- Rigid compared with Flow-driven logic.
- Less suitable for cross-object orchestration.
- Custom UI experiences are limited.
- Complex, branching enterprise scenarios quickly become awkward.
Pros of Flow Approval Process
- Much more flexible for branching, concurrency, and conditions.
- Better fit for modern Flow-first Salesforce architecture.
- Can combine approvals with automation and screen experiences.
- Scales better for enterprise process design when governed well.
Cons of Flow Approval Process
- More design, testing, and governance work.
- Audit and reporting need intentional architecture.
- Support teams may find custom implementations harder to troubleshoot.
- Flexibility increases the risk of over-engineering.
4) Field history tracking, audit trail, and compliance
Classic Approval Process audit model
Classic approvals come with a native approval history model and reporting support. Salesforce documents approval history reporting for classic approvals separately from the new Flow approval monitoring model. That native history is one reason regulated teams still prefer classic approvals for simpler use cases.
- Approval actions are automatically recorded.
- History is easier to expose in related lists and reports.
- Less custom work is required to prove who approved what and when.
Flow Approval Process audit model
Flow approvals provide monitoring and visibility, but if you want a durable, business-friendly audit model for enterprise reporting, comments, analytics, or compliance, you should usually design it explicitly. In practice, many teams store a custom approval event record alongside status fields on the main business object.
Does Field History Tracking work with Flow approvals?
Yes. Field History Tracking works on object fields regardless of whether the field was changed by a user, Flow, or Apex. So if your Flow approval updates fields such as Approval_Status__c, Approved_By__c, or Approved_Date__c, those changes can be tracked just like any other tracked field.
The key limitation is that Field History Tracking is not the same as a full approval history engine. It tells you that a field changed; it does not always give you the complete business narrative you need unless you design for it.
| Audit question | Classic Approval Process | Flow Approval Process |
|---|---|---|
| Can I see who approved? | Yes, natively. | Yes, if stored in fields, work items, or a custom audit object. |
| Can I track status changes over time? | Yes, through native approval history and reporting. | Yes, through tracked fields and/or a custom audit object. |
| Can I report on comments? | More straightforward in native approval reporting. | Usually requires custom design for reliable reporting. |
| Can I satisfy compliance needs? | Often easier for standard controls. | Yes, but architecture must be intentional and validated. |
Field History Tracking and Salesforce Shield
Standard Field History Tracking still has practical limits and retention constraints, while Salesforce Shield's Field Audit Trail extends long-term history retention and higher field-tracking scale. If your organization is in banking, lending, insurance, or healthcare, Shield can be a major part of a Flow approval compliance design.
- Use standard Field History Tracking for core status visibility.
- Use a custom approval audit object for business-readable approval events.
- Use Shield Field Audit Trail when long retention or higher audit scale is required.
5) Architecture patterns
Pattern A: classic linear approval
Best when the process is simple, sequential, and strongly record-centric.
Pattern B: Flow approval with audit design
Best when approval is part of a wider automation path and reporting must be customized.
Pattern C: orchestration-style enterprise workflow
Best for multi-stage enterprise processes where approvals are only one step in the end-to-end journey.
6) Enterprise example: loan approval workflow
Consider a lending process. A classic Approval Process can handle a straightforward manager sign-off, but a real loan workflow often needs more than that: document checks, external score validation, risk review, compliance review, and only then final approval. This is exactly the kind of scenario where Flow approvals and orchestration patterns become more attractive.
| Step | Business activity | Better fit |
|---|---|---|
| 1 | Loan application submitted | Either model |
| 2 | Automated data validation and credit checks | Flow approval / orchestration |
| 3 | Risk team review | Flow approval / orchestration |
| 4 | Compliance sign-off | Flow approval / orchestration |
| 5 | Manager approval | Either model |
| 6 | Disbursement or downstream processing | Flow approval / orchestration |
7) Final recommendation
- Use classic Approval Process for standard approvals that should stay easy for admins to support.
- Use Flow Approval Process for multi-stage, conditional, or integration-heavy workflows.
- Use a hybrid audit model for Flow approvals: tracked status fields + custom approval history object + Shield where needed.
- Do not choose Flow approvals just because they are newer. Choose them when the business process genuinely benefits from the added control.