# GB5 Dashboards: One Platform, Every View Your Clients Need

## The pitch

Every client wants their dashboards to look different — different KPIs, different charts,
different layouts for a sales lead versus a warehouse manager versus a CFO. GB5's Dashboard
framework makes that a configuration exercise, not a custom-build project: dashboards are built
from reusable **Pages** and **Portlets**, drawn from a governed catalog of **Portlet Types**, with
filters that cascade sensibly from the whole dashboard down to a single widget — and end users can
still make it their own without touching a single setting an admin controls.

## What it does for your implementation team

- **Build once, reuse everywhere.** A Page can appear on more than one Dashboard. A Portlet
  Type (Chart, KPI Card, Table, Analysis widget, …) is built once and placed as many times as
  needed, each with its own data and settings.
- **Filters that just work.** Set a filter at the Dashboard level and it applies everywhere
  underneath — unless a specific Page or Portlet needs to override it. No more re-configuring
  the same filter on every widget on a dashboard, and authoring a new filter is a couple of
  clicks, right where you're already setting it up.
- **Widgets that talk to each other.** A portlet can publish a value (say, a selected region)
  that another portlet on the same page subscribes to and reacts to — cross-filtering dashboards
  without custom JavaScript per client.
- **License-aware by default.** If a client's contract doesn't include a given dashboard or
  widget type, it's simply not offered to them — enforced automatically, with a safety-first
  design that never accidentally *hides* something a client is entitled to see.

## What it does for your end users

- **Pin your favorites.** Any user can pin the dashboards they use most to the top of their own
  list — a personal view, without needing an admin to change anything for anyone else.
- **Arrange it your way.** Drag and drop to reorder your dashboards; reset to the default
  arrangement any time.

## Under the hood (for a technical evaluator)

- Versioned Portlet Type registry — new capabilities roll out to a portlet type without
  breaking widgets already built against the previous version.
- A 4-tier filter precedence model (Dashboard → Page → Portlet → live user selection) that's
  explicit and predictable, not a pile of special cases.
- Entitlement-gated visibility with a deliberate fail-open safety design — a licensing-service
  hiccup never blocks a client from seeing something they've already paid for.

## Where this stands today

The backend is complete and live-verified, including inline filter authoring and a real
GB5-menu entry for several of the admin screens. The remaining admin screens implementation
teams will use are built and passing every automated check, reachable today via a direct link;
live in-browser screenshots and menu integration for the rest are the next milestone, expected
as part of ongoing rollout — this is an honest snapshot of a fast-moving build, not a finished
brochure.