> For the complete documentation index, see [llms.txt](https://docs.noros.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.noros.ai/features/dashboards.md). # Dashboards Save the charts, tables, and numbers you care about to a dashboard that keeps itself up to date. A dashboard is a saved visual view of your cloud data. You ask Noros for a chart, a table, or a single number, and Noros places that widget on the dashboard. The dashboard keeps each widget current, so you do not have to ask the same question again. Open **Dashboards** in the left sidebar. The feature is in beta. ### One dashboard per account Each account has one dashboard. Noros creates it the first time you open Dashboards. There is no dashboard list, and there is no second dashboard to switch to. The dashboard is not tied to one cloud account. Each widget reads the account it was built against, so a single dashboard can show AWS and Google Cloud together. ### Build a widget by asking The chat box at the bottom of the dashboard is the main way to build it. Describe the widget you want, and Noros adds it. **Try asking:** * "Add a chart of monthly cloud spend by service for the last 6 months" * "Add a KPI card for projected monthly spend" * "Show last month's top 10 resources as a table" * "Change the spend chart to a line chart" * "Remove the budget widget" A new widget shows a loading state while Noros runs the query behind it. A large query takes a few seconds. ### Pin a chart from a conversation Every chart and table in a Noros answer carries a plus button in its top right corner. Use it to put that visual on your dashboard without describing it again. The button offers two choices: * **Add and redirect to dashboard** opens the dashboard once the widget is ready. * **Add and stay** keeps you in the conversation, so you can add more first. KPI cards and text blocks cannot be pinned this way. Ask for those from the dashboard chat box. ### Widget types | Type | What it shows | | ---------- | ----------------------------------------------------------------------------------------------- | | Chart | Spend or usage over time, or a comparison across categories. Bar, line, area, stacked, and pie. | | Data Table | Rows of detail, with sorting. | | KPI Card | One number, with a trend and a sparkline. | | Text | A markdown note. Use it for section headings and context. | A dashboard holds up to 50 widgets. ### What a widget can read A widget can be backed by the same data Noros already answers on. This includes [cost breakdowns](/features/cost-breakdown.md), [cost trends and forecasts](/features/cost-trends-and-forecasting.md), [anomalies](/features/anomaly-detection.md), [budgets](/features/budgets.md), [reservation and commitment health](/features/reservation-and-commitment-health.md), [savings opportunities](/features/savings-opportunities.md), rightsizing summaries, FinOps score, [sustainability metrics](/features/sustainability-and-greenops.md), CostStreams, and [direct queries against your Cost and Usage Report](/features/advanced-data-querying.md). ### How current the numbers are Noros stores each widget's result and reuses it. It runs the query again when the stored result is more than 12 hours old, or when the period the widget covers moves on. Widget periods are relative rather than fixed. A widget built for "this month" reports the current month as the month advances. A widget built for a named date range stays on that range. ### Change the layout Select the dashboard title to rename it. Everything else is done by asking. Use the dashboard chat box to move a widget, resize it, retitle it, switch a chart to a different type, or take it off the board. **Try asking:** * "Make the spend chart a line chart" * "Move the KPI card above the spend chart" * "Make the anomalies table wider" * "Rename that widget to Monthly Cloud Spend" * "Delete the budget widget" ### Share a dashboard Select **Access** to open the Manage access dialog. Add a person by email address. A person you add can view the dashboard. That person cannot change it, and cannot use the dashboard chat box. A dashboard can be shared with up to 50 people. ### Export to PDF Select **PDF** to download the dashboard. The button stays disabled until every widget has finished loading, and it names the widgets that are still pending. ### When a widget shows an error A widget reports **Widget failed to render** when Noros cannot read the data behind it. Cloud account permissions are the most common cause. Ask Noros in the dashboard chat box what went wrong, and it reports the specific error for that widget. ### Example Conversations **Building a first view:** > "Add a chart of monthly cloud spend by service for the last 6 months, and a KPI card for projected monthly spend" > > Noros creates both widgets, places them on the dashboard, and takes you there. **Reworking a widget:** > "Make the spend chart stacked and limit it to the top 5 services" > > Noros updates the widget in place. Its title and position stay as they are. ### Go Further with North A Noros dashboard is one board that you build for yourself. North has purpose-built pages with customizable views for cost streams, visibility cost explorer, the commitment health ledger, and the anomaly timeline. [Learn more about upgrading →](/other/powered-by-north.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.noros.ai/features/dashboards.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.