Skip to main content
The Enterprise Admin Dashboard is Cardinal’s internal controlled-pilot operations view. It reads protected operational data from the Cardinal Protection API and keeps product readiness separate from roadmap work.
The current dashboard is password-gated for authorised Cardinal team members. It is not yet a production identity-and-access system. Before broader operational use, add named users, multifactor authentication, role-based access, session controls, access revocation, and an auditable administrator-change history.

​
Connected views

​
Metric interpretation

Dashboard metrics must include their scope and observation window when used outside internal operations.
  • API reliability is the success rate of recorded requests in the displayed pilot dataset. Do not present it as contractual uptime.
  • Average response time is calculated from recorded API activity. It does not replace external latency monitoring.
  • Threats detected counts recorded REVIEW and BLOCK decisions according to the current implementation. It does not represent confirmed crimes, sanctions matches, or prevented financial loss.
  • Decision distribution describes the current dataset. Demonstration traffic can materially influence the percentages.

​
Current operational gaps

The following data is not yet centrally ingested:
  • business-customer accounts, users, roles, and organisation settings;
  • customer-portal payment requests and their delivery state;
  • Escrow contract events and settlement reconciliation;
  • inbound support messages and tenant-scoped ticket history;
  • approved billing plans, invoicing, collection, and treasury reconciliation;
  • external service health, on-call alerts, and incident timelines.

​
Required production controls

Before treating the dashboard as an enterprise operations console:
  1. Replace the shared pilot password with named identities, MFA, SSO where required, and least-privilege roles.
  2. Record every administrative read and change with actor, time, tenant, reason, and outcome.
  3. Separate demonstration, staging, pilot, and production data visibly and technically.
  4. Add pagination, filters, export controls, retention rules, and redaction for sensitive records.
  5. Connect customer-portal records, Escrow events, support cases, billing, reconciliation, and external observability.
  6. Define incident severity, ownership, escalation, response targets, and customer-notification procedures.
  7. Test tenant isolation and administrator access through an independent security review.

Product status

Confirm the delivery state and production boundary for each Cardinal capability.

Support operations

Prepare a safe request and review the current support boundary.