MCM-12 — Nexus Admin Operational Visibility

← Back to MCM Nexus overview

As a Nexus Admin,
I want an at-a-glance view of trial activity, expiring subscriptions, and instance health,
so that I don't have to scan the full customer list to know what needs my attention.

Acceptance Criteria

• A summary dashboard shows counts of: active trials, trials expiring within N days, and pending requests awaiting review.
• Trials past their validity window are automatically transitioned from ACTIVE to EXPIRED by a scheduled job — no manual Nexus Admin action required to close out an expired trial.
• Customers approaching trial expiry (a configurable number of days out) receive an automatic reminder email (see Email Template below) prompting them to raise a Purchase or Extension request (see MCM-05).
• The dashboard surfaces organizations whose MCM instance has not checked in (see MCM-08) within an expected window, distinguishing "healthy and connected" from "gone quiet".
• The organization list shows each Organization's currently-installed MCM version (from MCM-08's periodic check-in), so the Nexus Admin can see at a glance who is running an outdated version.
• The summary dashboard also shows a count of releases awaiting approval (see MCM-33 — Release Catalog and Version Approval), alongside the existing trial/pending-request counts.

Technical Design

A scheduled job in mcm-nexus/backend (reusing/extending the existing expiry job, applied uniformly to demo and paid licenses) transitions licenses from ACTIVE to EXPIRED once past their validity window, and sends reminder emails via the shared send-email API (see MCM-11 — Shared Email API) as trials approach expiry. Two new endpoints, GET /api/admin/dashboard/summary and GET /api/admin/organizations?checkedInSince=..., back a new (admin)/admin/* summary dashboard, aggregating active-trial/expiring/pending-request/pending-release counts and surfacing organizations whose last successful validation (see MCM-08 — MCM Instance Subscription Validation) is older than the expected window. The organizations endpoint also returns each org's installedVersion, populated by MCM-08's periodic check-in, and the summary endpoint's pending-release count reads directly from MCM-33's Release table.

Email Template

Subject: Your MCM Trial Ends Soon — <Days Remaining> Days Left

Dear <Customer>,

Greetings from the MCM Team!

Your MCM trial for <Company Name> is ending soon.

## Trial Details

Role: <Enterprise or MSP>
Valid until: <trial end date>

To keep your MCM access uninterrupted, raise a Purchase or Extension request from your Nexus dashboard before your trial ends.

Portal: https://nexus.mcm.revdau.ai/dashboard

If you have any questions, our support team is available to help.

Support Email: mcm@revdau.ai
Documentation Portal: https://mcm.revdau.ai/docs/

Thank you for choosing MCM.

Best Regards,
MCM Team

UI / Frontend Changes

• New (admin)/admin/* summary dashboard page: at-a-glance counts of active trials, trials expiring within N days, pending requests awaiting review, and releases pending approval.
• Dashboard section listing organizations whose MCM instance has "gone quiet" (no recent check-in), visually distinguished from healthy/connected organizations.
• Organization list/detail view shows each org's currently-installed MCM version alongside its last-validated timestamp.
• Empty state: dashboard sections show a clear "nothing pending" message when counts are zero, rather than an empty table.
• No manual action required for expired trials — the dashboard simply reflects the scheduled job's ACTIVE → EXPIRED transitions as they happen.