Set approval policies and review who did what
Require sign-off on sensitive actions, and keep a record you can check when a number doesn't add up.
Before you start
- Team members added with roles assigned
Steps
Decide what needs a second look
Approval › Approval Policies lets you require sign-off on specific actions — a large payment out, a return above a certain value, a proforma invoice — before they take effect.
Set the approvers
Assign who can approve each policy. This is usually a level above whoever triggers the action, not the same person on both sides.
Work a pending approval
A blocked action — a payment out, an order return, an inventory outbound — sits waiting until someone with authority approves or rejects it in Approval, instead of going through unnoticed.
Review the trail
Activity Log › Audit keeps a record of who changed what and when, approvals included. You won't read it most weeks — but the week a number doesn't match what you expect, it's the fastest way to find out why.
What you end up with
Sensitive actions that get a second pair of eyes before they happen, and a record afterward of exactly who did what.
Modules used
Can't find what you need?
Tell us what you were trying to do. We read every message, and the questions we get here are what decide which guide gets written next.