Before enabling Workbench

What this prepares

The intended field user can enter Workbench, see only permitted modules and actions, protect local data on the device, prepare reference data while online, and continue approved work while offline.

Required access setup

• The user's role is marked Field Agent Role. Entity permissions alone do not open Workbench.
• Turn on Dashboard Access as well only when the same role should use both Workbench and the online Dashboard. A hybrid role still lands in Workbench by default.
• Grant only the required Workbench entity permissions. The create actions map to Create Customer Application, Create Account, Create Loan Application, Create Fixed Deposit Application, and Create Transaction.
• Set the user's tenant, primary branch, data-access scope, and Accessible Branches deliberately. Branch scope falls back to the primary branch when no additional branches are selected.
• Ensure the user's role and account are active and that any login-time working hours, weekend, or holiday restrictions allow the enrollment session.

See Dashboard and Workbench access, Roles and permissions, and Data-access scope.

Required operational setup

Complete the readiness checklist for every capture module the user will use:

• customer onboarding;
• account opening;
• transactions;
• loan origination;
• fixed deposits.

Workbench caches prepared reference bundles, but it does not invent missing products, policies, currencies, branches, transaction codes, customers, or accounts. Prepare each enabled module while the device is online.

Device enrollment

1. Use a supported browser or installed application on the device that will be used in the field.
2. Connect to the network and sign in as the intended user. The first online entry validates the Field Agent Role and prepares time-limited offline access for that user.
3. Set up local protection. On the web this is a passphrase of at least eight characters. On a supported native device, biometric or device-credential protection can be used, with passphrase fallback where offered.
4. Open each permitted module and prepare its offline data while online.
5. Confirm that queued work is empty and the last synchronization completed successfully before the device leaves connectivity.

The standard offline access period is one day from the last successful online validation. Reconnection is required after expiry. A different signed-in user, company, or installation may require local recovery or reset before the device can continue.

Required only when using this feature

• Link the user to an Agent record when customer ownership, agent assignment, agent account operation, or agent-branch context is required. The Workbench shell itself resolves from Field Agent Role; the Agent record is not the shell-access switch.
• If the user captures non-system FX rates, grant Override FX Rate and prepare the required rates and evidence rules.
• If the role can also use the Dashboard, verify both surfaces separately. A successful Workbench login does not prove Dashboard sidebar and route access.

Verify the setup

After the online enrollment and module preparation, take the device offline, close and reopen Workbench, unlock local protection, create a disposable draft, and confirm that it enters the local queue. Reconnect and confirm that it synchronizes exactly once and appears in the Dashboard within the same user's scope.

See Access, installation, and security and Prepare for offline work.