Appearance
Approvals workflow
Also known as
- approval
- approve
- reject
- approval rule
- approval chain
- threshold
- delegation
- escalation
- maker-checker
- four eyes
Approvals stop a document until the right people agree to it: a purchase order over a limit, a large stock adjustment, a leave request, a critical non-conformance. One approval engine serves every module. An account administrator decides what needs approval in Approval rules; approvers decide each request in the Approvals inbox; anyone can hand their approvals to a colleague while away in Delegations.
How an approval runs
- A user submits a document (Submit for approval). The document moves to Pending approval and becomes read-only.
- The engine looks for the active approval rules of that document type, lowest Priority number first, and takes the first one whose conditions all match.
- If no rule matches, the document is approved at once (the history records an automatic approval) and continues.
- Otherwise the rule's steps run in order. Each step names its approvers: a role, a person or the requester's manager. Any one approver decides needs one approval; Everyone must approve needs all of them.
- The approvers of the current step are notified ("Approval requested: Purchase order PO-2026-00012") and the request appears in their inbox.
- When the last step is approved, the document moves on (for example to Approved, or straight to Posted for a vendor bill). A rejection at any step ends the request: the document returns to the requester with the reason.
⚑ Approval
Every step marked ⚑ on a module or process page is decided this way. The rule that applies, and therefore who approves, is whatever your administrator set up in Approval rules; the demo company's rules are listed under Rules in the demo company.
Decide a request
- Select Approvals in the spine (the badge is the number waiting for you), or press Ctrl K and type
approvals. - Optional: narrow the list with Search number or summary or the Document filter.
- Select a request. The right side shows the Amount (for money documents), Document, Requested by, Requested, Current step and the Steps with each approver's decision.
- Select Open document to read the whole document first, if you need to.
- Decide:
- Approve: add an optional Comment and select Approve.
- Reject: write the Reason (required; the requester sees it) and select Reject request.
- Reassign: choose the New approver and select Reassign. That person decides this step instead of you.
You see "PO-2026-00037 approved" and the request leaves your inbox. In the dialogs, CtrlEnter confirms.
You can also decide from the document itself: when it is your turn, the document's Approvals panel shows Approve and Reject. When it is not your turn it says "Waiting for another approver."
Delegate your approvals while you are away
- Go to SettingsDelegations (every user can open it, even without other settings access).
- Select Delegate approvals.
- Pick the Delegate (a colleague), the Dates (first and last day) and, optionally, Document types. Leave the document types empty to delegate everything.
- Select Delegate. The delegation shows under My delegations with its status.
During those dates, requests waiting for you also reach your delegate. You can still decide them yourself. To stop early, select End delegation on the row.
Set up an approval rule (administrators)
- Go to SettingsApproval rules and select New rule.
- Under Rule, enter the Name (for example "Large purchase orders"), choose the Document, set the Priority (when several rules match, the lowest number wins) and leave Active on.
- Under When, select Add condition and build each condition as field, operator and value, for example Amount is at least
25,000. All conditions must be true. With no condition the rule applies every time. - Under Approval steps, for Step 1 choose the approver type (A role, A person or Requester’s manager) and add the approvers.
- Choose Any one approver decides or Everyone must approve.
- Optional: set Escalate after (hours) and Escalate to (a role). If nobody decides in time, the users of that role are added as approvers.
- Select Add step for a second level (for example a finance director after the department head). Steps run in order.
- Read the sentence at the bottom ("Purchase orders where amount is at least 25,000 need approval from the Finance role.") and select Save rule (or Create rule for a new one).
Fields you can test in conditions
Every document type offers Amount, Currency and the requester's role, plus its own fields:
| Document | Module | Extra condition fields (examples) |
|---|---|---|
| Purchase requisition | Procurement | cost centre, entity, source, line count, estimated total |
| Purchase order | Procurement | vendor, vendor group, entity, total, has contract, revision, blanket release |
| Vendor bill | Finance | party, party group, entity, match status, source module, total |
| Customer invoice | Finance | party, party group, entity, source module, total |
| Journal entry | Finance | journal type, journal code, entity, line count |
| Sales order | Sales & CRM | customer, customer group, total, Highest line discount %, Margin %, Credit override |
| Stock adjustment | Inventory | reason, warehouse, net value, total increase / decrease |
| Engineering change order | Manufacturing | priority, BOMs, changes, reason |
| Leave request | People | Leave type, days, org unit, employee group |
| Job requisition | People | org unit, headcount, employment type, reason |
| Timesheet, Expense claim | Projects | Total hours, Billable hours, resource, projects |
| Non-conformance report, CAPA, Document revision | Quality | severity, source, disposition, vendor, item, cost / priority / department |
| Planning scenario | Planning | kind, entity, fiscal year, net income |
| Policy version, Data subject request | Compliance | category, version / request type, subject type |
Where approvals appear
| Module | Documents that can need approval | Where the approver acts |
|---|---|---|
| Procurement | Requisition, Purchase order | Approvals; thresholds also in Approval defaults |
| Finance | Vendor bill, Customer invoice, Journal entry | Approvals |
| Sales & CRM | Sales order (discount, margin, credit limit) | Approvals |
| Inventory | Stock adjustment | Approvals |
| Manufacturing | Engineering change order | Approvals |
| People | Leave request, Job requisition | Approvals, managers also in team approvals |
| Projects | Timesheet, Expense claim | Approvals |
| Quality | Non-conformance, CAPA, Document revision | Approvals |
| Planning | Scenario | Approvals |
| Compliance | Policy version, Data subject request | Approvals |
Each of these documents shows an Approvals panel with the status, the steps and the approvers (Documents and their states).
Rules in the demo company
| Rule | Document | Applies when | Approver |
|---|---|---|---|
| Procurement: requisitions ≥ 2500 | Purchase requisition | amount at least 2,500 | a role (managed from Approval defaults) |
| Procurement: purchase orders ≥ 25000 | Purchase order | amount at least 25,000 | Finance role (managed) |
| Large vendor bills | Vendor bill | amount at least 20,000 | a role |
| Large sales orders | Sales order | amount more than 25,000 | a role |
| Large stock adjustments | Stock adjustment | amount more than 2,500 | a role |
| Leave: manager approval | Leave request | always | requester’s manager |
| Requisitions: HR approval | Job requisition | always | a role |
| Critical NCR dispositions, CAPAs from audits, Controlled document revisions | Quality documents | severity critical / source audit / always | a person |
Permissions
| What | Who |
|---|---|
| Decide a request | The approvers the rule assigns (or their delegates). No extra permission is needed. |
| Submit, recall | Whoever may create the document in its module. |
| Create and edit approval rules | Account administrators; the API permission is Permission: settings.workflow.manage. |
| Delegate your own approvals | Every user. |
Limits and things to know
- If a step resolves to nobody (for example Requester’s manager for a user without a manager, or a role with no active users), the request goes to the account administrators instead, so it never gets stuck.
- Changing a rule affects new submissions only. Requests already pending keep the steps they started with.
- Recall cancels the pending request; submitting again starts a new one (the document's Approvals panel then says "1 earlier request · Open in approvals").
- An inactive rule never matches. Without any rule for a document type, its documents are approved as soon as they are submitted.
- Escalation is checked regularly in the background, not at the exact minute.
- Leave days and timesheet hours are not money, so the inbox shows no amount for them.
- For approvals added on the fly by an automation, see the Require approval action of Workflow rules.
