Review approvals and sensitive actions
Assess evidence, organization, scope, and consequences before approving, rejecting, sending, posting, paying, or filing.
Who can do this
A member with review or approval authority
Primary route
/approval
Last verified
4 August 2026
01
Verify before acting
Approval is a control, not a queue-clearing task.
- Confirm the active organization and record owner.
- Open the source document, request, or provider evidence.
- Check scope, amount, recipient, period, and downstream effect.
- Confirm you are authorized and independent from the preparer where required.
- Approve, reject, or return with a concise reason.
02
Treat agent output as a proposal
An agent may summarize, draft, classify, or prepare an action. Verify factual claims and attachments before permitting a consequential tool action.
Never paste credentials, one-time codes, private keys, full identity numbers, or payment authentication into the assistant.
03
Verify completion in the system of record
A platform approval may authorize the next step without proving that an external bank, provider, or agency completed it.
- Open the resulting platform record and check status/history.
- For bank, provider, or government actions, confirm the external acknowledgement.
- Attach or reference the acknowledgement according to policy.
- Escalate partial, duplicate, or unexpected completion immediately.
04
Respond to suspicious activity
Stop work and notify the organization administrator if you see another tenant’s data, unexplained access, changed credentials, unknown approvals, or a request to bypass controls.
Troubleshooting
- The approval lacks evidence: return it to the preparer; do not infer missing facts.
- You approved by mistake: report it immediately and use the supported reversal or cancellation path.
- External status is unknown: verify at the provider, bank, or agency before retrying to avoid duplication.