1. What the Showcase is

The Ivanti MCP Showcase is a centrally hosted gallery of Ivanti Neurons & ITSM dashboards built on the Model Context Protocol (MCP). It lets you:

• Browse a curated catalog of ready-made dashboards (ITSM, patch, exposures, full-solution walkthroughs, and security-advisory storytelling).
• Rate each dashboard from 1 to 5 stars so the team knows what resonates.
• Send feedback — request a scenario, ask for a new dashboard, suggest an improvement, or share a dashboard you built yourself by attaching its HTML.

You sign in with your organisation identity (Entra ID / SSO). Tenant credentials are held server-side and are never exposed to you — the dashboards fetch their data through a server-side proxy, so there is nothing to configure and no secrets to handle.

2. The catalog — three categories

The landing page groups every dashboard into three fixed sections, always shown in this order:

Each dashboard tile shows

• A title and description.
• Solution tags (AEM, NSG, ITSM, APM) — you can filter the catalog by these using the chips at the top of the page.
• A data badge — Snapshot for sample/demo data, or Live refresh for a dashboard wired to live MCP data.
• Its star rating aggregate (see next section).

3. Rating a dashboard

Every dashboard card carries a 1–5 star rating at the dashboard level.

• On the catalog page, each tile displays the average rating and the number of votes so you can see at a glance which dashboards are most valued.
• Inside an open dashboard, a small floating rating bar (bottom-right) lets you cast or change your own score.

How it works

1. Sign in — the rating control is disabled until you are signed in.
2. Click a star (1–5). Your vote is saved immediately.
3. One vote per person, per dashboard. If you rate the same dashboard again, your previous score is updated, not added — so the average reflects one opinion per user.
4. The catalog average and count refresh to include your vote.

Ratings are anonymous in the aggregate — the catalog only shows the average and total count, never who voted.

4. Sending feedback

Open Share feedback from the catalog header. The form gates on sign-in and shows who you are submitting as (read-only — your identity comes from your signed-in session, never from a field you can edit).

4.1 Feedback types

4.2 What you can include

• Details (required) — up to 10,000 characters describing the idea, scenario, or improvement.
• Context — why this matters (optional) — the decision, risk, or outcome it supports.
• Your role / job title, Organisation / customer, and Use-case scenario / industry (all optional) — this context helps the team prioritise and curate.
• An attachment (optional) — a single file up to 10 MB. Allowed types are images (PNG, JPG, GIF, WebP), PDF, or an HTML dashboard.

4.3 Attaching an HTML file to be deployed as a new catalog item

This is the key path for contributors who have already built a dashboard:

1. Choose the feedback type “Share a Dashboard I Created” (or “Request a new dashboard” if you're proposing one you built).
2. In Add attachment, select your .html dashboard file (single file, up to 10 MB).
3. Describe the scenario and business context the dashboard supports in the Details/Context fields — this is what the team uses to curate it.
4. Submit. Your submission (and its HTML file) is stored for review.

From here an admin reviews the submission. If it is accepted, the admin can promote the HTML attachment into a published catalog dashboard. Once published, it appears in the User Generated Samples section of the catalog for everyone to open — served safely in a sandboxed viewer. Admins can later unpublish or remove it, and can re-promote it from your original submission if needed.

5. Admin capability (informational — for non-admins)

Most people use only the catalog, ratings, and feedback form above. A small set of authorised admins have an extra review area. This section is purely informational — if your account isn't an admin, the admin page will tell you it is not authorized for admin review, and none of the actions below are available to you.

What admins can do

• Review incoming feedback — filter submissions by type and status, and read the full context (submitter, role/organisation, scenario, and any attachment).
• Categorise feedback — run an LLM-assisted pass that tags each item with a category, priority, and sentiment to speed up triage.
• Decide on each item — mark it Accept, Reject, or Needs info.
• Generate requirements — consolidate one or more accepted items into structured requirement drafts.
• Promote dashboards — turn an accepted new_dashboard / share_dashboard item that has an HTML attachment into a published catalog dashboard (this is the step described in §4.3), and later publish/unpublish or remove promoted dashboards.
• Toggle live refresh on eligible dashboards.

Admin access is granted through your organisation's identity provider (a specific app role / group). There is nothing for a non-admin to configure — the capability simply stays hidden and inaccessible unless your account is authorised.

6. Quick reference