Dashboards Overview

Dashboards give users a fast operating view of the areas they are allowed to work with. They bring together summaries, charts, pending work, recent activity, and quick actions so users can see what needs attention before opening the underlying workspace.

Dashboards are not the final audit record. Use them to monitor and prioritize, then open the related module when you need to approve, correct, post, allocate, settle, or reconcile a record.

Workspace Reference

Dashboard	How Users Reach It	What Users Usually Do There
General Dashboard	Dashboard -> General Dashboard	Review broad KPIs, approvals, recent activity, trends, and quick actions.
Teller Dashboard	Dashboard -> Teller Dashboard	Open sessions, post teller transactions, review drawer balances, return float, and close sessions.
Loan Officer Dashboard	Dashboard -> Loan Officer Dashboard	Review lending pipeline, repayments, collections, arrears, and portfolio follow-up.
Approval Items	Dashboard -> Approval Items	Review pending operational and finance approvals.
Dashboard Configuration	Administration -> General Setup -> Configurations -> Dashboard Configuration	Arrange dashboard sections and widgets for the service.

What Controls What Users See

The dashboard layout is controlled by three things:

• Service access determines which business areas are relevant for the current service.
• Permissions determine which cards, sections, and actions are visible to the signed-in user.
• Dashboard configuration determines the order of sections and whether a section is visible or hidden for the service.

If a user cannot see a dashboard section, it does not always mean there is no data. It may mean the section is hidden, the service does not use that feature, or the user does not have permission to view it.

General Dashboard

The general dashboard is the broad operating dashboard. It can include financial metrics, deposits, loans, shares, inventory, assets, HR, CRM, communication, driving school, approvals, system activity, teller operations, recent transactions, and quick actions.

Use the business-unit and period filters before interpreting the figures. A card shown for one business unit or period may not match the total shown in a report or a module workspace with different filters.

Typical sections include:

• Financial cards and trends for revenue, journal activity, and business-unit performance.
• Deposit and loan portfolio cards for account counts, balances, arrears, risk, and movement trends.
• Shares, stock, asset, HR, CRM, communication, and driving sections when those modules are active for the service.
• Pending approvals and latest activity so managers can see review work and recent user activity.
• Recent transactions and quick actions for common follow-up paths.

If a dashboard card shows an error or stale information, refresh the card or open the source module to confirm the current state.

Dashboard Configuration

Administrators can configure how the general dashboard appears for a service. The configuration screen lets an administrator:

• Reorder dashboard sections to match the service’s operating priorities.
• Hide sections that are not useful for that service.
• Re-enable hidden sections later without rebuilding the dashboard.
• Reorder cards and charts inside each enabled section.
• Review unsaved changes before saving.
• Ignore changes when the draft layout should be discarded.

A hidden section stays in the saved dashboard flow but does not render for users until it is made visible again. This is useful when a service is not yet using a module, or when a team wants a simpler dashboard for daily work.

Good configuration practice:

• Keep high-frequency operational sections near the top.
• Hide sections for modules the service does not actively use.
• Avoid showing sensitive sections to roles that only need task-level views.
• Revisit the layout after introducing a new module or service profile.

Teller Dashboard

The teller dashboard supports day-to-day teller work. It is focused on the current teller session, cash drawers, posting actions, float handling, and daily transaction review.

Users can:

• Select an open business day and available till when starting a session.
• Open a till session before processing teller transactions.
• Review currencies available for the session.
• Post teller transactions when a session is active.
• Review drawer balances and expected cash.
• Return float where the drawer supports that action.
• View daily entries and transaction history.
• Open transaction details for review.
• Count drawers and close the till session.

The close-session process expects drawer counts to be entered correctly. If a variance or denomination mismatch is shown, review the drawer counts before closing. Teller dashboard values should be reconciled with the detailed teller and accounting views when investigating differences.

Loan Officer Dashboard

The loan officer dashboard is a role-focused dashboard for lending teams. It helps loan officers prioritize sales pipeline, collections, arrears, repayments, and portfolio follow-up.

Common sections include:

• Pipeline snapshot and pipeline mix.
• Collection pace against target.
• Upcoming repayments.
• Client portfolio.
• Disbursement versus collection trend.

Use it to decide who needs follow-up today, which repayments are due soon, and where the portfolio needs attention. For account-level decisions, open the loan account or client record from the relevant module before taking action.

Approval Items Dashboard

The approval dashboard groups pending review work. It separates general operational approvals from finance posting approvals where applicable.

Users can:

• Review counts by approval area.
• Filter to a specific approval domain.
• Open approval item details.
• Review the operation, status, approval number, and extra information captured with the request.
• Move to the source workspace when deeper review is needed.

Approvals should not be decided from summary counts alone. Open the item detail, check the underlying business record, and confirm the operational or financial impact before approving or rejecting.

Reading Dashboard Values

Dashboard values are summaries. They may differ from detailed reports when:

• The dashboard is filtered by a different business unit or period.
• A module workspace applies additional statuses or approval filters.
• A transaction is pending approval, posting, settlement, or reconciliation.
• A section is hidden or unavailable because of permissions.
• A background refresh has not completed yet.

When totals matter for finance, audit, or settlement decisions, use the source workspace or approved report as the final reference.

Common Mistakes

• Treating a hidden section as proof that the service has no records in that module.
• Comparing dashboard totals with reports without matching business unit and period filters.
• Approving records from counts without opening the approval detail.
• Closing a till session without reviewing drawer variances.
• Using loan officer summaries instead of the loan account detail for client decisions.
• Leaving unused dashboard sections visible for roles that do not need them.

Good Practice

Start each day by checking the dashboard for pending approvals, exceptions, follow-ups, and operational readiness. Use the dashboard to decide where to go next, then complete the actual work in the appropriate module workspace.