An approval process makes sure a record that meets certain conditions is approved by an authorised person before it proceeds. The best-known example is a quote with a discount above a certain rate.
Building blocks
- Entry criteria: Which records require approval? (e.g. discount > 15% or amount > 500,000 TRY)
- Approver: A specific person, a role or a team.
- Steps: Some records go first to the sales manager, then to the finance manager.
- Outcome: Approve or reject, both recorded with a reason.
Why it matters
An approval process does not forbid exceptions; it makes them visible. The record answers who approved what, when and why.
In CRModular
Approval processes define entry criteria, approver type (user, role or queue) and multi-step progression; a record awaiting approval can be locked and field updates can be applied on the outcome. Only the assigned approver or an administrator can decide. For quotes, the approval and its comment are written to the quote history. Details: Automation: rules, approvals and flows.