Bank Administrator

The bank administrator has the first operational workspace after deployment.

The bank administrator initializes the token, registers organizations, creates wallets and deposit token accounts, maintains roles and limits, reviews activity, and configures the application presentation.

Log in as the bank administrator user with the wallet granted the Token Admin Besu contract role when the smart contract was initialized. The wallet must be eligible for the configured organization and wallet service instance. This user can log in before a deposit token account is created. Create the remaining users’ wallets and deposit token accounts before they log in.

Before you begin the administrator tasks, the application must be deployed, either by one-click deployment or local deployment, and configured so that it is connected to the Besu contracts, wrapper API service, wallet service, and other supporting services. You must also have the following information.

Bank administrator login details from smart contract initialization, to open the application and complete administrative setup before an operational deposit token account exists.
The token ID and token description supplied for the deployment. The token description is handled during token initialization; account creation uses the selected token ID and account details.
Organization names, unique organization IDs, and the intended founder/participant order. Organizations must be registered before accounts can be created for them.
User IDs and eligible wallets for the users who will operate the application. Each operational account is linked to a user and an active wallet.
The application group and daily limits required for each user. The selected group controls the workspace and the configured limits control account usage.

Typically the bank administrator completes tasks in the following order.

Open the system dashboard.
Initialize the token if deployment has not already initialized it.
Register the founder and participant organizations, and then confirm their display names and sequence order.
Create wallets and deposit token accounts for the bank administrator and other bank personas.
Create accounts for participating organization administrators. After participating organization administrators create their manager accounts, use the Sync Roles command on those accounts to add the escrow ledger role.
Review or update token details and configure the transaction purposes before operational token transfers begin.
Review the account list, organization cards, KPIs, and analytics dashboard.
Configure the application settings and customize the application presentation.

The following tasks are typical ones that a bank administrator completes.

Initialize Token

Initializing the token is the first task that the bank administrator must complete.

Select Token Management > Initialize Token. The Initialize Token window opens.
Confirm that the token ID is correct.
Edit the customer-facing token description as needed, including the Currency, Currency Description, and Conversion Rate. Optionally, select Purpose and then select one of the configured purposes.
Select Initialize Token to complete the process.

You must register organizations before you create accounts for them. Use the organization sequence to control the order in which organizations are displayed in the application.

Select Participants > Organizations. The Manage Organizations window opens.
Enter an Organization Name, Organization ID (the unique ID used by the network registry), and a Sequence number. The founder organization is always first in the sequence. If the requested sequence is already in use, the selected organization and later entries move to preserve a valid order. The application also reconciles missing, duplicate, or non-consecutive values using the registry data and creation order. If the live registry contains more than one founder, correct the founder tags in the registry before continuing.
Select Register Organization.

Create Wallets and Deposit Token Accounts

Complete the following steps to create accounts.

Select Participants > Create Bank Account. The Create Token Bank Account window opens.
Select the Bank Name, and enter the Bank User ID.
Select Load wallets for the configured wallet service instance.
Select the user's wallet, or if the user has no eligible wallet, create a wallet. To create a wallet, select Create new wallet. Loading or creating wallets for another organization might require that organization’s wallet service instance ID.

Select the Group and set the account limits.

The following table describes the account information fields.

Field	Description
Token ID	The ID of the token that was initialized for the system.
Bank Name	A list of all registered organizations in the network.
Org ID	The organization ID of the bank, which is determined by the selected Bank Name.
Bank User ID	A user ID for the account.
Role	A list of supported roles. Role information is supplied by the selected application group. Roles are assigned by the application during account creation.
Group	A list of application groups (personas).
Daily Maximum Amount	The maximum amount of tokens that can be transacted per day.
Daily Maximum Transactions	The maximum number of transactions allowed per day.
Wallet	Select an active wallet with no existing token account. Use Load wallets to retrieve eligible wallets or Create new wallet when the deployment permits wallet creation.

Select Create Account. The account details are displayed.

The selected application group and its associated roles are assigned automatically, with the except of a institution manager. After creating a participating institution manager account, open its account actions menu and select Sync Roles to apply the required escrow ledger role. Application groups determine the workspace shown in the UI; ledger roles determine contract operations.

Work with Governance

The bank administrator can access the Bank Governance workspace to maintain user compliance controls and amount-based transfer approval policies.

To adjust compliance controls for a specific user, select the user and update the following fields.

KYC: The identity verification state used by configured compliance checks.
AML: The anti-money-laundering state used by controlled transfer checks.
Risk: The risk value associated with the user for policy evaluation.
Restriction: The restriction state, which can prevent a controlled operation.

To adjust approval policies, select the policy and update the following fields.

Amount range: The lower and upper value amounts for the policy.
Status: Activates or deactivates the policy.
Approver organization: The organization responsible for an approval step.
Approver user ID: The user responsible for an approval step.
Order: Moves approvers into a sequence.

A policy with no approvers can settle a matching transfer immediately. With one approver, the transfer is routed to that approver, who must explicitly approve or reject it. A policy with multiple approvers advances sequentially. Completed approval steps remain recorded. For a request that is still pending, remaining approval routing is evaluated using the active policy. A policy’s organization ID and user ID must match an active bank approver account with an eligible wallet.

Additional Administrator Tasks

Select Token Management > Manage Purposes to add, edit, or remove the purpose values that are available for transfers. Removing a purpose does not rewrite existing transaction history.

Select Insights > Analytics Dashboard to open the read-only dashboard. From the summary cards, select the Accounts, Transactions, or Token view. Choose an organization and status for a narrower set of results. Select Refresh Analytics when the page was opened before a recent operation completed. A "No analytics data" message means the selected view has no available records or is still loading; adjust the filters or refresh the page.

Select Account > My Account to open a read-only page for the currently logged-in user. You can use this page to confirm the account selected at sign-in, its organization and token, its status and balance, its limits, and the changes recorded for the account.

Troubleshooting

If organization or account data is unavailable, verify the UWaaS, wrapper API, smart contract, wallet, and ORDS configuration. If a role is missing, use the Sync Roles command and ask the user to log out and log in again so that the session is rebuilt.