RBC Express User Management: Role-Based Access Control
RBC Express User Management is the access control layer that sits above every payment, report and administrative action in the commercial portal. Company Administrator provisioning. Role templates. Per-account permissions. Dual-control thresholds. RBC Secure Key token assignment. Seven-year audit retention. This is how Canada's largest Schedule I bank handles access — applied to your commercial operations.
Your CFO sees everything. Your AP clerk touches only supplier batches. Your auditor views reports but cannot initiate. Your treasury lead approves wires. Your controller provisions new users but cannot approve their own additions. RBC Express User Management enforces the separation — not suggests it.
Sign In to Manage Users Read the Security Model
The Five Role Templates in RBC Express
Start with a template. Override at the per-account or per-product level. Nothing is one-size-fits-all inside RBC Express User Management.
Initiator
Creates payment batches and individual transactions but cannot release. Typical AP clerks, junior treasury analysts, payroll administrators. In RBC Express User Management, Initiators have no standing authority to move money — they hand off to Approvers.
Approver
Reviews and approves payments initiated by others, up to configurable thresholds. Typical finance managers, controllers, treasury leads. The RBC Express User Management engine enforces that an Approver cannot approve transactions they initiated themselves — separation of duties is structural.
Auditor
Read-only access to every report, every transaction detail and the full audit trail inside RBC Express User Management. Typical internal auditors, external auditors granted temporary access, compliance officers. Auditors cannot initiate, approve or modify anything — they observe.
Administrator
Company Administrator (super-user) provisions delegated users, assigns role templates, configures dual-control thresholds, issues RBC Secure Key tokens, maintains GL mappings and distribution lists. Typical treasurer, CFO delegate, IT liaison. RBC Express User Management supports multiple Administrators with dual-control on administrative changes.
Read-Only
View balances and pre-built reports. Cannot export, cannot initiate, cannot approve. Typical executives needing visibility, non-finance department heads, board observers. RBC Express User Management Read-Only is the minimum meaningful access level.
Custom Roles
Combinations that do not match a template — for example an AP Initiator with Read-Only on FX, or an Approver limited to a single subsidiary’s accounts — configure per-permission inside RBC Express User Management. Company Administrators save custom roles as reusable templates for their organisation.
Permission Matrix by Role
Default capability grid inside RBC Express User Management. Every cell is overridable per-account and per-product.
| Role | Initiate | Approve | Release | Reports |
|---|---|---|---|---|
| Initiator | Yes | No | No | Limited |
| Approver | No | Yes (to threshold) | Yes | Full read |
| Auditor | No | No | No | Full read + audit |
| Administrator | No (separate Admin) | Admin changes only | No | Full read + config |
| Read-Only | No | No | No | Balances + dashboards |
Dual-Control Thresholds in RBC Express
Above a configurable amount, every payment requires a different user to approve. Below it, the Initiator can release solo if authorised. The threshold is yours to set inside RBC Express User Management.
Per-Product Thresholds
Wires trigger dual-control at a different amount than EFT batches. FX contracts above a notional threshold require a second approver. Bill payments have their own threshold. RBC Express User Management keeps each product line's rule set separate so risk appetite can vary by payment type. Canadian dollar and foreign currency thresholds can be configured independently.
Three-Person Workflows
For the highest-risk transactions — real estate closings, acquisition payments, dividend distributions — RBC Express User Management supports three-person workflows: Initiator, First Approver, Second Approver, Releaser. Each of the four must be a different user. This is the control model insurers and auditors ask about during enterprise risk reviews, and it is native to RBC Express User Management.
Access Profile
- RBC Express User Management = five ship role templates plus unlimited custom roles.
- Company Administrator is the super-user — provisions, configures, revokes. Cannot self-approve.
- Dual-control thresholds per product, per account, per currency. Three-person workflows available.
- RBC Secure Key tokens assign through the console; revoke remotely or via 1-800-769-2555.
- Audit log retention 7 years — searchable by Company Administrator via the standard report engine.
RBC Secure Key Token Assignment
Every RBC Express User Management user needs a second factor. The Company Administrator issues it.
Inside RBC Express User Management the Company Administrator requests a token for a new user. RBC ships the physical RBC Secure Key device or activates the mobile RBC Secure Key app to the user's registered phone. On first sign-in the user binds the token to their credentials through the RBC Express Login flow. Lost tokens can be revoked remotely by the Company Administrator or by phoning the RBC Express Service Centre at 1-800-769-2555 during a loss, theft or separation event. The revoked token cannot be used to sign in even if the password is known — the RBC Express User Management binding is broken at the bank side.
Separation events (employee leaves the organisation) follow the same remote-revoke path. Best practice is to revoke the token before the final pay cycle so the departing user cannot sign in to RBC Express User Management-governed surfaces after their last day. The RBC Express audit trail records the revoke event and every subsequent denied sign-in attempt.