Approval Processes

Automation 🟢 Beginner
📖 5 min read

Definition

Approval Processes is a Setup page where administrators define multi-step approval workflows that route records to designated approvers based on criteria. Each process specifies entry criteria, approval steps with assigned approvers, and actions to take upon submission, approval, rejection, or recall of a record.

Real-World Example

The admin at Granite Financial creates an Approval Process for discount requests on Opportunities. Any discount over 15% requires manager approval, and anything over 30% also requires VP approval. When a sales rep submits a 25% discount, the Opportunity locks and an approval notification is sent to the rep's manager. If approved, the discount field is updated and the rep is notified.

Why Approval Processes Matters

Approval Processes solve the critical business problem of ensuring that certain records require authorization before proceeding. Without them, a sales rep could unilaterally approve large discounts, finance could bypass expense limits, or contracts could be signed without legal review—creating compliance risks and revenue leakage. Approval Processes enforce accountability by locking records during the approval journey and routing them to designated decision-makers based on specific criteria like dollar amount, department, or custom field values. This is fundamentally different from other automation like workflows or flow, which execute actions; Approval Processes specifically create a human decision gate with a formal audit trail.

As organizations scale and governance requirements tighten, the absence of proper Approval Processes creates chaos. Multiple approval hierarchies may bypass each other, records get approved by unintended people, and there's no visibility into who actually approved what and when. Real-world consequences include regulatory violations (especially in finance and healthcare), unexpected budget overruns, discounted deals that should have been rejected, and security risks from improper access approvals. When Approval Processes are poorly designed—with unclear entry criteria, missing approver reassignment rules, or no timeout handling—records can get stuck in approval limbo, frustrating teams and blocking business operations. Proper Approval Process architecture becomes essential once an org has more than a handful of users requiring different approval thresholds.

How Organizations Use Approval Processes

  • Vertex Manufacturing — Vertex implemented an Approval Process for purchase requisitions on a custom Procurement object. Any requisition under $5,000 auto-approves; $5,000–$25,000 requires department manager approval; and over $25,000 requires both manager and CFO approval. By configuring this multi-step process with automated email notifications and locked record state during approval, they reduced maverick spending by 34% and cut procurement time from 5 days to 2 days. The approval audit trail also satisfied their annual SOX compliance audits.
  • Meridian Healthcare Solutions — Meridian created an Approval Process for medication discount requests submitted by their sales team to hospital systems. Any discount over 10% requires approval from the regional clinical director to ensure patient safety isn't compromised by over-aggressive pricing. When a rep submits a request, the record locks and an approval task is generated for the director. Upon approval, a custom workflow updates the quote and sends it to the hospital; upon rejection, it notifies the rep with the reason. This process ensured medical and business review happened for every significant discount, reducing liability exposure.
  • Pinnacle Talent Group — Pinnacle built a complex Approval Process for job offer letters with dynamic routing based on position level and hiring manager. Entry-level offers auto-approve after HR validates credentials. Manager-level offers route to the department VP. Director and above route to both the VP and CHRO. Using <strong>Approval Process Actions</strong>, they configured the system to generate the final offer letter document upon final approval and automatically email it to the candidate. They also set a 5-day timeout rule so stuck approvals escalate to the next level, ensuring offers reach candidates within their competitive window.

🧠 Test Your Knowledge

See something that could be improved?

Suggest an Edit