Approvals are how your team uses AI without losing control. Every sensitive action should be reviewed before it reaches a buyer, supplier, internal owner, or connected business system.Documentation Index
Fetch the complete documentation index at: https://docs.theubik.com/llms.txt
Use this file to discover all available pages before exploring further.
What needs approval
- Buyer replies with price, promise date, or quantity commitments
- Margin changes or exceptions
- System updates
- PO extraction and SKU mapping
- Customer updates after ETA movement
- Actions that use sensitive customer, supplier, or pricing context
What each button means
| Action | Use when |
|---|---|
| Approve | The suggestion is correct and ready to move. |
| Edit | The direction is right but the copy, data, or owner needs adjustment. |
| Assign | Another operator, finance reviewer, or admin needs to decide. |
| Reject | The recommendation is wrong, stale, or unsafe. |
Reviewer checklist
Approval means accountability. Check source context, not just the drafted output. If the context is stale or missing, assign or reject the item instead of approving it.
- Source thread matches the customer or supplier.
- SKU, quantity, unit, and account mapping are correct.
- Pricing and margin are within the agreed guardrail.
- The action does not reveal internal notes or sensitive context.
- The activity trail will explain the decision later.