Dashboard

What the dashboard shows

The Dashboard is the first page after sign-in. Every authenticated local user can open it; there is no separate dashboard permission. It remains available when the license has no optional Modules or when the installed OneView version does not yet support a newly licensed Module or Sub-module.

Every user sees the safe signed-license phase. Additional dashboard details follow the same permissions as their destination pages; the dashboard does not introduce or require a dashboard:* permission.

• With license:read, Signed license shows phase, edition, subscription/perpetual type, commercial expiry, active vendor connections, and monthly executions. Capacity bars stop visually at 100%, while their text retains the safe actual and limit values so an over-limit state is not hidden.
• With verifications:read, Licensed verification Sub-modules links to each permitted Sub-module's locally stored history.
• With vendors:read, Vendor readiness compares licensed Sub-modules with active local connection configuration and links to the vendor-connections page. Users with vendors:manage receive management guidance; readers receive review-only wording.
• With updates:read or updates:manage, available or staged update notices link to System updates. License expiry and grace/block notices reuse the same safe alert rules as the application header.

While status is loading, the dashboard exposes an accessible message. Failed license, vendor-summary, or update-status requests show a safe error and Try again action.

The dashboard does not change the license, create a vendor connection, or initiate a verification. Open a licensed Sub-module under its Module group, such as KYC → BVN, to review its history or start a new check.

KYC → PEP Screening and KYC → Sanction Screening are separate entries when both are licensed and installed. Their readiness and usage are assessed separately; neither entry means the other screening will also run.

The license summary can describe a purchased Module or Sub-module before its pages become available in navigation. This means the license has been refreshed but the installed OneView version may not contain it yet. Check License & Updates → System updates and follow Modules, Sub-modules & adapters. Functionality that works without adapters does not need a vendor connection before its navigation can appear.

Run a browser verification

1. Open the required licensed Sub-module under its Module group, such as KYC → BVN.
2. Select New Verification on that Sub-module's page. The Sub-module is already selected and cannot be changed in the drawer.
3. Choose an active Vendor connection for that Sub-module.
4. Optionally enter a concise Purpose in the single-line input. Leave it blank when no purpose should be recorded. When supplied, the trimmed value must contain 3–240 characters and must not include a BVN, NIN, name, phone number, address, or other identity or KYC value.
5. Complete the service-specific fields shown below the purpose.
6. Review the Sub-module, connection, any supplied purpose, and subject fields, then select Run verification once.
7. Keep the drawer open while OneView completes the synchronous request.

OneView applies retry protection automatically to browser verifications. There is no idempotency-key field for the administrator to complete.

The form remains visible beside the persistent result panel on wider screens and above it on narrower screens. After completion, the result panel shows Verification completed, the normalized status, and Normalized result, or a safe failure. The normalized result is a read-only structured JSON view; review it in the drawer rather than trying to edit it. Submit another verification only for a genuinely new approved request. Verification results can contain personal data; do not copy them into logs, tickets, screenshots, or chat.

A browser verification uses licensed execution capacity and the selected provider may charge for it. Do not submit again after an uncertain outcome until you review the displayed result and Verification history.

Use the summary safely

A healthy-looking summary is not a substitute for operational checks:

1. Review full signed state and refresh controls under License management.
2. Configure and inspect providers under Vendor connections.
3. Open the required Sub-module under its Module group to run an approved check or review earlier outcomes in Verification history.
4. Use Network health checks and the sanitized installation report for host-level health.

For example, 3 / 5 active connectors describes licensed capacity; it does not mean those three providers accepted a live request. A monthly execution count may include failed attempts because a provider can accept and bill a request without returning a successful result.

The dashboard never requests verification history, raw KYC request/result data, consent evidence, vendor credentials, activation codes, or signed-lease token material. Dashboard screenshots can still include commercially sensitive license capacity, Module and Sub-module names, and organisation branding. Apply the client's screenshot and support-redaction policy before sharing them.