Help · Approvals and actions
A finding, a request, an action, and a check that it worked.
The product may recommend. Only a person may approve. Once approved, the action is carried out against your records, written to the audit trail, and re-checked later to see whether the condition actually went away. Nothing in that sentence is optional.
The chain
Exception → recommendation → request → execution → verification.
| Step | Who | What it is |
|---|---|---|
| Exception | Detection, every fifteen minutes | A condition in your records that needs a decision, with the figure, the formula and the rows. |
| Recommendation | An agent, reading only your data | What could be done about it, in words, with the evidence it read. A recommendation with no executable action stops here. |
| Request | The product | A card on the Approvals screen saying exactly what will happen — generated from the action's own inputs, never from prose — and why a person is being asked. |
| Decision | You | Approve, reject, or ask for more information. Rejecting requires a reason; the next reader learns from it. |
| Execution | The product, once | The change is made to your records and an audit row records before, after and who. |
| Verification | The product, later | The original condition is re-checked. If it is still there, the exception is re-escalated rather than quietly closed. |
The seven actions
What the product can actually do.
Expedite a purchase order, cancel one, raise a purchase requisition, increase safety stock, reallocate stock between plants, reschedule a production order, change a customer's promise date. That is the whole list. Anything else — releasing a payment, changing a supplier or a contract, deleting a transaction, altering master data — is on a block list that always needs a person, written down before the product could do any of it.
Autonomy levels
How much a person is asked.
Your organisation sits at a level from 1 to 5. At level 1 the product observes and says nothing about actions. At level 2, the default, it recommends and every action waits for approval. Levels 4 and 5 would let low-risk, reversible actions run unsupervised; they are switched off in this release, so every action waits for a person whatever level is set.
Reaching your ERP
Only with the switch on, and only three actions.
If a connection has write-back switched on, an approved expedite, cancel or requisition is also written to that ERP after it succeeds here, and the card shows the ERP's own reference. If the ERP refuses, the card says so and offers a retry; your records here stand either way. See connectors and write-back.