MCM-03 — Request a Hosted Enterprise Demo

← Back to MCM Nexus overview

As a Customer User,
I want to request a 30-day Enterprise trial inside RevDau's own shared MCM environment,
so that I can evaluate MCM without deploying anything myself.

Acceptance Criteria

• The request form clearly labels this option as running inside RevDau's shared environment, not the customer's own infrastructure.
• Before submission, the customer must see and explicitly acknowledge (checkbox, not just a banner) a data-sharing disclosure stating that cloud account metadata and discovered resource data connected during the trial will be processed and stored in RevDau's shared demo environment and is accessible to RevDau support staff for troubleshooting.
• Submission is blocked until the disclosure checkbox is checked; the acknowledgment (who, when) is recorded against the request.
• The form collects only what's needed to create the demo Enterprise on the Demo Instance — Company Name, and the requester's own name/email as the demo Enterprise's admin user — the customer never sees or picks a billing plan; that's pre-configured by the Nexus Admin (see below). The Enterprise's domain is taken from the customer's already-verified Nexus organization domain, not asked again.
• On submission, a request of type Hosted Enterprise Demo is created with status PENDING and routed to the Nexus Admin for review via MCM-06 — Nexus Admin Review, Approve, and Reject Requests.
• The customer sees the request in their request history with its current status and the disclosure they agreed to.
• The Nexus Admin, ahead of time, configures the Demo Instance connection in Settings: the Demo Instance's base URL, and an MCM MSP Admin email/password Nexus uses to authenticate to it. Nexus then fetches the Demo Instance's available billing plans and the Nexus Admin selects exactly one plan per module; this selection is reused for every subsequent demo Enterprise creation until the Nexus Admin changes it.
• The Nexus Admin cannot approve a Hosted Enterprise Demo request until at least the required billing plans are configured — the approve action is blocked with a message pointing to the Demo Instance settings page otherwise.
• The moment the Nexus Admin approves the request, the demo Enterprise is created behind the scenes — Nexus calls the Demo Instance's own enterprise-creation API directly with the request's details and the Nexus Admin's pre-selected billing plans; no further manual action is needed on RevDau's side.
• If the Demo Instance is unreachable or rejects the creation call, the request shows an actionable failure state (with a retry action) rather than silently remaining PENDING or falsely showing APPROVED.
• If approved and successfully created, the resulting license is scoped to the Enterprise role for a 30-day validity window from the approval date.
• The activation email for this request type is its own template (see Email Template below), not the standard Subscription Activation email — it drops the Deployment Guides and MCM App credential sections entirely, since nothing is installed on the customer's side, and instead gives the requester the login URL for their new demo Enterprise inside RevDau's shared environment.
• This email carries no password or credential of any kind. The demo Enterprise's admin account is created (from the request's name/email) by the same call that provisions the tenant, but with no password set by Nexus — the Demo Instance's own existing account-creation flow separately emails the requester directly to set their password before they can log in, independent of and not sent by Nexus.

Technical Design

A new Nexus-Admin-only (admin)/settings/demo-instance page stores the Demo Instance's base URL plus an MCM MSP Admin email/password in a new DemoInstanceConfig entity (single row, password encrypted at rest, never returned to the frontend after save — encryption mechanism to be decided at implementation time). mcm-nexus/backend uses those credentials to call the Demo Instance's real POST /auth/login (email+password, matching mcm-api's existing AuthController), then GET /billing-plan to list its plans grouped by ModuleType (DISCOVERY, ORCHESTRATION, FINOPS, OBSERVABILITY, GOVERNANCE, SECOPS, DEVOPS); the Nexus Admin picks one plan per module and Nexus stores the chosen plan IDs on the same config row. Backed by the existing RequestService.create(...) (extended with HOSTED_ENTERPRISE_DEMO and the disclosure-acknowledgment field, as before), approval in MCM-06 now also calls the Demo Instance's real POST /enterprise with enterpriseName (Company Name), domain (the requester's Nexus organization domain), email/firstName/lastName (the requester, as the demo Enterprise's admin user), and the stored billing plan IDs — matching that API's actual EnterpriseRequest payload shape exactly, so there's no field-mapping guesswork at build time. Once the Enterprise is created, Nexus sends its own activation email (see Email Template below) via the shared send-email API (MCM-11) with the demo Enterprise's login URL and no credentials; separately and independently, the Demo Instance's own existing account-creation flow emails the requester directly to set their password on the new admin account — that email is not sent or controlled by Nexus.

Email Template

Exact content of the activation email for a Hosted Enterprise Demo — distinct from the standard Subscription Activation email, since nothing is installed by the customer and no MCM App credential exists for this path:

Subject: Your MCM Enterprise Trial is Ready

Dear <Customer>,

Greetings from the MCM Team!

Your 30-day Enterprise trial is now ready inside RevDau's hosted demo environment — there is nothing for you to install.

## Access Your Demo Environment

Login URL: <Demo Instance URL>

You'll receive a separate email directly from the demo environment with instructions to set your password. Use that password, together with this email address, to sign in at the URL above.

## Trial Details

Organization: <Company Name>
Role: Enterprise
Valid until: <trial end date>

If you have any trouble accessing your trial, 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

<Demo Instance URL> is the base URL the Nexus Admin configured for the Demo Instance (see Technical Design above) — not a fixed domain, since it points at whichever shared environment the Nexus Admin has connected. The separate password-setup email is sent directly by the Demo Instance itself as part of its own existing account-creation flow, and is outside Nexus's content or control.

UI / Frontend Changes

• New (admin)/settings/demo-instance page: Demo Instance URL field, MCM MSP Admin email field, MCM MSP Admin password field (masked, write-only — never redisplayed in plaintext after save).
• "Fetch Billing Plans" action on that page, showing plans grouped by module with a single-select per module, and a "Save Selection" action.
• The settings page shows the last-saved plan selection (plan name only, not raw IDs) and lets the Nexus Admin change it at any time.
• (customer)/requests/new: Hosted Enterprise Demo option clearly labelled as running inside RevDau's shared environment, distinct from self-hosted request types. No billing-plan field on this form — the customer never sees one.
• New data-sharing disclosure checkbox component, with the submit button disabled until it is checked.
• Request history / detail view shows the recorded disclosure acknowledgment (who, when) alongside the request's status, plus an actionable retry state if Demo Instance creation fails.
• In MCM-06's Nexus Admin review queue, the Approve action for this request type is disabled — with a message pointing to Demo Instance settings — until at least the required billing plans are configured.
• Duplicate-pending state: if a pending request of this type already exists, the form surfaces that existing request instead of allowing a second submission.

Out of Scope

• Supporting more than one Demo Instance — the Nexus Admin configures a single shared demo environment.
• Editing a demo Enterprise's billing plans after it's been created — the pre-selected plans only apply at creation time.