Skip to main content

​
Insights hub orientation

The Insights hub is the landing grid at /insights that groups every analytics surface in the dashboard into one navigable tile set — the answer to “where do I go to look at the numbers?” when you open the sidebar’s Insights entry. Insights hub grid Each row below is a hub tile. Tiles marked future have no read guide yet — the page works, the gap is in the docs tree.

​
The tile model

Every section card answers four questions before you click:
  • Name and one-line description — the surface’s headline metric and scope, with an icon.
  • Native vs Cross-link badge. Native tiles route under /insights/<name>; a Cross-link badge means the tile hands off to a surface that lives in a sibling tree (the omnichannel wallboard, the voice tree, the quality hub) — the badge’s hover hint reads “Lives in another section of the dashboard.”
  • Coming soon badge. Occasionally a tile ships pre-launch as a teaser: the route exists and is navigable, the underlying endpoint ships later. Read-intent tiles lose the badge when their endpoint goes live.
  • Role-gating. A handful of tiles only render for an allow-listed seat (see RBAC visibility). The filter is the same normalised org role the sidebar uses, and the destination page re-checks it server-side — the tile hide is presentation-only, never an authorisation boundary.

​
RBAC visibility

Three gating families live on the hub:
  • Finance cluster — Channel Costs, LLM spend, Sustainability, Agent ROI, and Agent comparison render only for owner/admin/developer/billing seats. A viewer or agent sees none of these tiles, and the destination page 403s them regardless — the grid simply avoids showing a surface a role can’t read.
  • CDP-family cluster — Retention, Funnels & Retention, Account Scores, and Auto-drafted knowledge render only for owner/admin/developer, mirroring the read gate over the PII-bearing customer-event stream.
  • Quality cluster — Quality Management renders to owner/admin, Performance Leaderboard to owner/admin/supervisor, and QA Evaluations also to agent (an agent sees only their own evaluations page).
Everything else on the hub — Analytics, Logs, KPI Alerts, Usage anomalies, Usage alert rules, Reports, SMS Click-Through, Link Tracking, Conversation Intelligence, Contact Reasons, Topic Intelligence, Sentiment, Journey Paths, High-friction sessions, Deliverability, Conversion Goals, Attribution, Marketing mix model, Surveys, AI Containment, Per-language AI quality, Search Analytics, the two wallboards, Voice Quality, and Scheduled Reports — renders for every member, including viewers, because its read route is genuinely member-readable. Writes on alerting rules stay owner/admin/developer-gated at the API, but the read views are open.

​
How to navigate

In the dashboard, open the sidebar’s Insights entry — the hub is its landing page. Direct URLs work the same: /insights renders the grid, and any tile href (/insights/<route> for native tiles, the absolute path for Cross-link tiles) is bookmarkable. The hub headers two live stat rows above the tiles — a 24-hour API-count / latency / messages / agents row and the flagged-transactions strip — and one cross-link row below. Use the sidebar only when you want the grid again; every tile name doubles as its direct route segment for scripting or sharing links.

​
Section map

​
Role-specific views

Two worked examples of the same hub, one per seat:
  • A viewer or agent opens the grid and never sees the finance cluster (Channel Costs, LLM spend, Sustainability, Agent ROI, Agent comparison) or the CDP-family cluster — every tile they do see is one their role’s read route is entitled to, so the grid is always the full set of what they can open. An agent additionally sees QA Evaluations (their own evaluation scores, acknowledge/appeal workflow) but not the org-wide Quality Management rollup.
  • An admin sees every tile on the grid including the finance and CDP families, because their seat passes the hub’s normalised-role filter and the destination page’s server-side guard in the same way.

​
Fraud alerts strip

Below the stat row, the hub renders the flagged-transactions strip — the top open fraud alerts raised on this account’s spend traffic. Each alert deep-links to its evidence; the strip collapses entirely when the fraud-shield queue is empty rather than rendering an empty container. For alert triage, verdicts, and the how-it-scans model, see the Compliance fraud shield guide.

​
See also