Use case · By usage
Agents that wait for a human yes.
Read first; every change becomes an approval request.
“An agent can change records with nobody watching.”
Control in three steps
Read first; every change becomes an approval request.
Check who is asking
Every person and agent is named, with a role from your directory.
Allow, ask or decline
Inside the role it runs. Changes wait. Outside the role, declined.
Record it
Every step lands in the audit trail.
See it work
Watch it happen.
Step 1 of 4: Request
“Move the repayment date on loan LN-5520 to 30 November.”
Every request starts with a named person and a named agent.
Simplified example. Names and records are invented.
Text version
Joy N. (Loans Officer) asks Loans agent: "Move the repayment date on loan LN-5520 to 30 November." The role check returns: Approval required. Human approval: Approved with an edit. Every step is written to the audit log.
01 Request
Joy N. · Loans Officer · Loans agent
Move the repayment date on loan LN-5520 to 30 November.
02 Role check
Approval required
- Role
- Loans staff (from your directory)
- Read
- Allowed
- Change
- Needs approval
Read-only first. Changes wait for a person.
03 Human approval
Approved with an edit
- Approver
- Credit supervisor
- Action
- Change repayment date, 1 loan
- Risk
- Medium
- Expires
- In 30 minutes
The supervisor corrects the due date before approving. The agent runs only the approved version.
04 Audit log
- 09:14:02 · request · joy.n · loans-agent · update_loan LN-5520
- 09:14:02 · policy · role=loans-staff · read=allow · change=approval_required
- 09:14:03 · approval · sent to credit-supervisor
- 09:21:47 · approval · modified and approved by peter.o
- 09:21:47 · executed · approved version only · result=success
- 09:21:47 · logged · event 7f3a…e21 · on the record
Questions
Short answers. Ask us anything else on the call.
See this in your own organisation.
Start with a free assessment. Two weeks. Read-only.
A one-page answer for your CEO and CISO. Assessments are offered at our discretion.