Skip to main content
Apragya AIFree quotation builderQuotation builderQuote builderno signup
Approvals

Build an Approval Workflow Without Code: Limits, Levels and Approvers Set by the People Who Own Them

For finance heads, purchase managers and HR leads who want approval rules they can change themselves, and proof of who approved what.

A finance head arranging tokens on three stepped shelves

You can build an approval workflow without code when the rules are settings, not programs. Most approval rules are simple: above this amount, this person signs; above that, a second person signs too.

The trouble is where those rules live. In many companies they sit in an email habit or a WhatsApp group, so a large purchase order gets approved by whoever replies first.

This page covers what informal approvals cost, an illustrative example, and how approval policies work in Apragya.

An example: a Ludhiana bicycle parts maker

Take an illustrative manufacturer where purchase orders were approved by the owner on WhatsApp. As volumes grew, the finance head wanted a clear rule: small orders by the purchase manager, larger ones by finance and the owner.

One purchase order under the new policy

  1. Order raised

    A buyer submits a large steel order.

  2. Condition matched

    The amount crosses the second threshold.

  3. Level one

    The purchase manager approves.

  4. Level two

    Finance head and owner, both required.

  5. Released

    The order goes to the supplier with its trail.

Level two needs both signatures, so neither can release a large order alone.

The policy took the finance head under an hour to set up. Orders now wait for the right people, the buyer can see where each one is, and when the owner raised the limit a month later, he changed one number.

An order sheet with two wax seals side by side
Two seals, because large orders now need both signatures.

What informal approvals cost

Wrong sign-offs

Large spends approved by whoever replied first.

Stuck requests

Nobody knows who is holding an order.

No proof

Auditors ask for approvals that live in chat threads.

Self-approval

People approve their own requests when no rule stops them.

How the multi level approval system works

Step 1 of 5

Policy

Name the record type the policy applies to, such as purchase orders.

  1. Policy: Name the record type the policy applies to, such as purchase orders.
  2. Conditions: Set when it applies, for example amount above a threshold.
  3. Levels: Add levels in order: manager, then director, then owner.
  4. Approvers: Pick a person, a role or a field such as the reporting manager; require all, any, or a number.
  5. Timeouts: Optionally let a level approve itself after a set time.

Choosing approval workflow software in India

Separate approval tools need the request copied in and the answer copied back. When approvals run on the purchase order, invoice or expense itself, the decision and the record stay together, and an auditor can see both.

Email approvals against Apragya policies

FeatureEmail and chat approvalsApragya approval policies
RulesHabitWritten as conditions and levels
Who approvesWhoever repliesNamed people, roles or fields
Parallel sign-offHard to enforceAll, any, or a set number
Own requestsPossibleCannot approve your own
RecordChat historyActivity log on the record

Checked against public information on 16 September 2026.

What sets Apragya's no-code approval process apart

On the record

Approvals sit on the order, invoice or claim itself.

One inbox

Approvers see their pending items in one place.

Parallel approvers

Legal and finance together, or any two of three.

Audit trail

Each action is recorded with user and time.

AI checks first

Agents can check a request before it reaches a person.

Change it yourself

Thresholds and levels are settings, not code.

See approvals in PO approvals, contract approvals and the approval queue.

Getting started

  1. Write down the approval rule people already follow, even if it is informal.
  2. Turn it into conditions and levels.
  3. Set the policy on one record type first.
  4. Run it for a month and note the requests that felt wrong.
  5. Adjust thresholds, then add the next record type.

The first month's odd cases tell you more about your real rule than any meeting.

What it costs to start

Free
Up to 3 users
CRM, HR and Vendor Onboarding
INR 3,999
Starter, a month
Up to 10 users, CRM and HR plus a choice of apps
INR 7,999
Pro, a month
Up to 25 users and every enterprise app

Approval workflow questions

Which records can carry an approval policy?
Policies apply to record types such as purchase orders and invoices, and apps like contracts, expenses and journal entries have their own approval steps.
Can two people have to approve together?
Yes. A level can require all listed approvers, any one of them, or a set number such as two of three.
Can approvals follow the reporting line?
Yes. An approver can be taken from a field such as the requester's reporting manager.
Can someone approve their own request?
No. The requester cannot approve their own request.
Can we change a limit later?
Yes. Thresholds and levels are settings an authorised admin can change.
What does it cost to start?
The free plan covers up to 3 users with CRM, HR and Vendor Onboarding and 1,000 AI Credits a month. Starter is INR 3,999 a month for up to 10 users, with CRM and HR plus a choice of apps such as Sales and POS, Inventory, Payroll, Purchase and Payables, Support and Manufacturing. Pro is INR 7,999 a month for up to 25 users with every enterprise app, including Finance and Accounting, plus 5,000 AI Credits, single sign-on and audit logs.

Write your approval rule down, then switch it on

Set one policy on purchase orders and let it run for a month.