Permission by responsibility
Role and department rules decide who sees a record and who can act on it.
Flowwiz / Controls & auditAgents do the work.
[Controls]
Agents do the work.
You set the boundaries.
Approval limits, confidence thresholds, and escalation rules are yours to define. Sensitive actions route to a person first.
Approval where it matters
Anything outside policy routes for human sign-off before it executes.
A trail that explains itself
Context, decision, and action recorded together, so any outcome can be reconstructed.
Control points
Where the platform stops and a person starts.
The controls are configuration, not policy language. Each one is a threshold or a rule you can point at.
- 01Access
Role and department permissions decide visibility and action rights.
- 02Threshold
Amount, category, and vendor rules decide what can auto-approve.
- 03Confidence
A confidence floor decides what the agent may act on unsupervised.
- 04Review
Anything outside those bounds stops for a named approver.
- 05Record
The decision, the approver, and the action are written to the audit trail.
What you configure
- What runs automatically
- What requires approval
- Confidence thresholds
- Approval limits
- Escalation rules
- Segregation-of-duties controls
- Role-based permissions
- Human-in-the-loop review points
What that guarantees
- No payment above limit without a person
- No action on low-confidence classifications
- No self-approval where segregation of duties applies
- No reminder sent after a promise has been captured
- Every automated action traceable to the rule that fired
- Every classification recorded with the input it came from
FAQ
Before you go further.
Does automation remove approval?
It does not have to. Review is configured around the decisions your team needs to control, and everything else is recorded instead.
How do we evaluate access and security?
Review role permissions, department access, approval requirements, and audit records with the Flowwiz team against your own policy.
Can we enforce segregation of duties?
Yes. Approval routing enforces SOD rather than assuming it, and self-approval can be blocked outright.
What is in the audit trail?
The input, the classification, the rule applied, the approver, and the action, timestamped and traceable to the record concerned.
Can permissions differ between AR and AP?
Yes. Visibility and action rights are scoped by role and department, so the two sides can be governed separately.
Start
See it with your team’s context.
Bring your workflow, your systems, and who approves what.