Business online banking users and entitlements
How do we change business online banking users and limits on an administrator's request with dual approval and a record of who authorized what?
Make every entitlement change a request with two approvals in it. When a business administrator asks to add, remove or change a user, a role or a limit, Callvu prefills the current entitlements, classifies the change against the business's own approval rule and the bank's policy, routes the second approval to another authorized administrator in the Decision Desk, and writes the change to online banking with both approvals, the before and after values and the time on the record.
In scopeSimpleCallvu moves: decide, write back
Last updated November 7, 2026.
The problem today
A user was added by a phone call to treasury support, and six months later moved fifty thousand dollars.
A business administrator calls treasury support to add a user with wire rights, or to raise a user's limit before a big payment. Support makes the change. Whether the caller was an administrator, whether the business's own rule required a second person, and what the limit was before, is in a call note. When the user turns out to have been a fraudster, or an employee who exceeded their authority, the business and the bank argue over who authorized it.
Business online banking is where the bank's security procedure under UCC Article 4A lives. The entitlements define who can do what, and a change to them is a change to the procedure. The interagency guidance expects dual control on administrative changes and limits, and the bank's record of who asked and who approved is its defense.
The requests are frequent and small, which is exactly why they are made by phone and why they need a process.
How it runs
From the requestto the system of record.
A business administrator requests an entitlement change in online banking, by a link, or on a call with treasury support. Callvu identifies the administrator against the business's entitlements and opens the request.
- Business administrator
- Requests the change and, for the second approval, another authorized administrator approves it on their own screen.
- Treasury support
- Starts a request from a call and sees its status; does not make the change.
- Callvu
- Prefills, classifies, routes the second approval, writes the change and records.
Identify and prefill
The requester is authenticated and checked for the administrator role on the business's profile. The current users, roles, limits and approval rules are prefilled, and the requested change (add or remove a user, change a role, change a limit, change the approval rule itself) is captured with the before and after values.
Classify
The change is classified against the business's approval rule (dual administrator approval for payment-capable roles and limits, for example) and the bank's policy (a cap on limits by relationship tier, a bank review for an approval-rule change). The classification sets who must approve and whether the bank must review.
Decide
The second approval goes to another authorized administrator in the Decision Desk on their own authenticated screen, with the before and after values. A change the bank's policy reserves (an approval-rule change, a limit above the tier cap) goes to treasury operations as well. The new user, where added, enrolls through their own link and is identified.
Write back
The change is written to online banking with both approvals, the people, the values and the time, the business receives a confirmation to the administrators, and the entitlement report is produced from the record.
Where it ends: The entitlement change is live with two authorized approvals, the before and after values and the time on the record, and the business and the bank can both show who authorized it. The Decision Trace shows the classification and the approvals; the Audit Trace shows the request, each approval and the write.
Runtime enforcement
What is enforcedwhile the work runs.
The regulations preloaded in Callvu Studio and the bank's own policies, applied as steps that run, not lines in a binder. A step that breaks a rule does not run, so a completed run was compliant.
The handoff
Between the front doorand the back office.
The front door
Online banking, a link, or a call to treasury support; approvals happen on each administrator's authenticated screen.
The back office
Treasury operations reviews only reserved changes; the change is written by the process with both approvals.
The Decision Desk
- The second administrator approves in the Decision Desk with the before and after values; a reserved change also goes to treasury operations with only the allowed outcomes.
Proof
In scope.Proof at scale, not one process at a time.
The kind of process Callvu runs in production for customers in this industry. Ask for a reference on this exact process. The results below are the industry's published proof; each claim code links to its record on agents.callvu.com.
Questions
What buyers ask next,answered plainly.
Can one administrator add a user with wire rights?
Not alone, where the business's rule or the bank's policy requires dual approval. The second administrator approves on their own screen, and the user enrolls through their own link.
Can treasury support make the change on a call?
No. Support starts a request; the administrators approve it; the process writes it. The call note is not the authorization.
What does the business get?
A confirmation to all administrators and an entitlement report with every change, who requested it, who approved it and when.
Related processes
Bring this process, or the one that costs you most.
We build it against your policies and your systems, train your team and stay with you through launch. You are live in weeks.