How to Set Up an Approval Process in Zoho CRM (Step by Step)

A sales rep quotes a 40% discount to close a stalling deal, hits save, and nobody with budget authority ever sees it until the invoice lands. That gap is exactly what an approval process closes, and it's one of the first guardrails our Zoho CRM consultants put in when a client tells us deals are slipping through unchecked. The good news is you can learn how to set up an approval process in Zoho CRM in an afternoon.

An approval process in Zoho CRM is an automation rule that intercepts a record before it moves forward, routes it to a designated approver based on criteria you define, and locks it until that person approves or rejects it. Think discounts above a threshold, high-value deals, or new vendor records that need a manager's sign-off. It sits under Setup, and any admin with Manage Automation permission can build one.

Which Zoho edition do you need, and where does it live?

Approval processes are an Enterprise edition feature (and up, including Zoho One). Professional and Standard users won't see the menu and would need to upgrade. If you're on Enterprise, head to Setup > Process Management > Approval Processes and click Create Approval Process.

One caveat worth naming before you build: approvals are not the only automation that gates a record, and picking the wrong tool creates friction you'll fight for months. We'll come back to that.

How does the approval flow actually work?

Every approval process is built from three moving parts: a criteria (which records trigger it), an approver (who decides), and actions (what happens on approve or reject). A record that meets the criteria gets locked, routes to the approver, and only unlocks once a decision is made and the follow-up actions fire.

While a record waits, Zoho locks it against edits, deletes, and conversions except for the specific fields you allow. That locking is the whole point: it stops the deal from advancing until the right person has looked.

How to set up an approval process in Zoho CRM, step by step

Here's the sequence we follow on client orgs, using a discount-approval example on the Deals module:

1. Name it and pick the module. Go to Setup > Process Management > Approval Processes, choose Deals, and give it a plain name like "Discount over 15% approval."

2. Set the rule criteria. Define what triggers approval — for example, Discount (%) is greater than 15. Only records matching this get held. Keep the criteria narrow; a broad rule gates records that never needed a second look.

3. Choose the approver. You can name specific users, a role, a group, or use the role hierarchy via Levels — 1st level routes to the record owner's direct manager, 2nd level to the manager above that. With multiple approvers, decide Anyone vs. Everyone and sequential vs. parallel routing.

4. Define approve actions. On approval, you can update a field (set Discount Approved to true), send an email alert, assign a task, or trigger a webhook or custom function to push the next step.

5. Define reject actions. On rejection, notify the owner and, ideally, update a status field so the record re-enters editing rather than sitting in limbo.

6. Set editable fields and activate. Decide which fields a rep can still touch while the record is locked, then save and turn the process on. Submit a test record before you let the team near it.

A rejected record with no reject action is a dead end. Always give the owner a path back into editing.

Approval vs. validation rule vs. Blueprint — which one?

This is where most orgs go wrong, so use the distinction plainly:

• Validation rules block a bad save — a missing field, an invalid value — instantly, with no human in the loop. Use them for data quality.

• Approval processes insert a person to sign off on an otherwise valid record. Use them for authority: money, discounts, contracts.

• Blueprint enforces a whole stage-by-stage process, guiding a record through a defined pipeline with conditions at each transition. Use it when the entire lifecycle needs structure, not just one gate.

If you want to see how the fuller process engine works, our guide to Zoho CRM Blueprint covers that side, and the Zoho CRM workflow automation guide covers rules that fire without a human at all. As a Business systems consultant team, we usually layer all three rather than force one to do another's job.

Want a second set of eyes on your automation design? Book a free Zoho consultation and we'll map your gates before you build them.

What's the most common mistake?

Over-gating. Teams get excited and route everything through an approver, and the pipeline seizes up. The cost is real: McKinsey research cited by workflow analysts finds knowledge workers waste up to 30 to 40 percent of their time waiting for decisions or clarifications instead of doing the work. Every approval you add is a potential bottleneck, and a single unavailable approver stalls every record behind them.

The fix is discipline in the criteria. Gate the 5% of records where authority genuinely matters — the outsized discount, the high-value contract — and let the other 95% flow. Name a backup approver, or use Anyone routing among a group, so one person's vacation doesn't freeze the board. A tight Zoho integration with clear approval logic speeds deals up; a sloppy one buries them.

Where this leaves you

Setting up an approval process in Zoho CRM comes down to three decisions — what triggers it, who approves, and what happens next — plus the judgment to gate only what truly needs a human. Build the criteria narrow, give rejections a way back, and keep validation rules and Blueprint in their own lanes. If you'd rather design it right the first time, book a free Zoho consultation with our team.

By the CodeStringers Team — Zoho Experts & Custom Software.

CodeStringers is a custom software engineering firm with a dedicated Zoho practice. We write from the automations, integrations, and process work we've actually shipped for clients — not from the manual.