Cost Dashboard Design: Best Practices for Shared Dashboards
A cost dashboard earns its place by answering one audience's routine question in one glance. Everything else belongs in a report.
Dashboard personalization is tailoring which views of cost and operations a given audience sees first: an executive, an engineering lead, and a FinOps analyst look at the same estate for different reasons. Done well, each group opens its dashboard and gets the answer it came for. Done badly, everyone gets the same crowded page and stops opening it.
Design around the question, not the data
Before choosing widgets, write down the question each audience asks every week.
| Audience | Routine question | Widgets that answer it |
|---|---|---|
| Leadership | Are we on plan, and where is the money going? | Headline totals, cost trend, budget health |
| Engineering | What will change in my environments, and did last night’s schedule run? | Upcoming actions, schedule activity and success rate, top costly resources |
| FinOps | Where are the savings, and who owns the spend? | Recommendations, showback, cost reports |
A widget that does not answer the audience’s question is noise on that dashboard, even if it is useful elsewhere.
Practices that hold up
- Keep it short. A dashboard that needs scrolling to reach its main chart has too many widgets. Put the answer at the top at full width, and supporting detail below it.
- One copy of each view. Two cost trend charts with different defaults invite the question of which is right.
- Share a default. Give the organization one landing dashboard so a new member sees the same starting picture as everyone else, and add audience dashboards alongside it.
- Clone, then edit. Start from a preset close to what you need rather than from a blank grid; you inherit a layout that already works at a glance.
- Make permissions visible, not broken. If a viewer cannot see a widget’s data, the layout should say so in place instead of collapsing into a different shape for each person.
- Change deliberately. Shared dashboards shape how people read the numbers. Record who changed what, and announce changes to the default.
How ZopNight dashboards work
ZopNight dashboards are organization-shared: admins compose them from a curated widget library, the organization has one default that every member lands on, and additional dashboards appear in a header switcher. Four built-in presets cover common audiences: Executive, Engineering, FinOps, and All Widgets. Presets cannot be edited or deleted; you clone one to customize it. If no default is set, members land on All Widgets.
The library has thirteen widget types, including headline stat cards, cost trend, cloud spend, cost reports, top costly resources, recommendations, quick insights, budget health, showback, and schedule activity and success-rate widgets. Each widget takes one of three size tokens, Wide, Standard, or Compact, on a fixed slot grid, and most widgets can be added once per dashboard. A widget whose permission a viewer lacks renders a no-access placeholder, and a widget that fails to load falls back to a placeholder instead of breaking the page. Creating, updating, deleting, and switching the default are recorded in the audit log.
Viewing requires the dashboard view permission; creating, editing, and deleting need the matching permissions, which the built-in Editor and Admin roles hold and Viewer does not. Limits are 50 dashboards per organization and 50 widgets per dashboard. Per-user dashboards, free-form resizing, template variables, and public share links are deliberately outside the current scope.
For the numbers behind the widgets, see the Sankey cost breakdown and cloud budgets; for access control, see RBAC; for a worked example, see how to configure a dashboard for the FinOps team.
Questions we get a lot.
If yours isn't here, email us and we'll answer directly.
Can each user have a personal dashboard in ZopNight?
Not today. Dashboards are organization-scoped and there is no per-user default. Create audience dashboards, such as one for engineering and one for FinOps, and use the header switcher.
What happens if the default dashboard is deleted?
The default pointer is cleared automatically, and members land on the All Widgets preset until a new default is set.
Can I edit a built-in preset?
No. Presets are immutable. Clone the preset into a saved dashboard and edit the copy.