> ## Documentation Index
> Fetch the complete documentation index at: https://docs.insight.nobly.dk/llms.txt
> Use this file to discover all available pages before exploring further.
# Viewing dashboards
> Open, filter, explore, and export reporting dashboards in Nobly Insight.
This page is for anyone who reads and explores a dashboard someone has built. You don't need to know how a dashboard was made to get value from it.
You'll see a dashboard in your list if you have the **View Reporting Dashboards** permission and belong to a user group it was shared with. If a dashboard you expect is missing, check that you have both — ask an administrator about the permission, and whoever built the dashboard to add your group.
## Open a dashboard
Open Reporting from the navigation and pick a dashboard from the side navigation. Dashboards are grouped there by **category** — with an *Uncategorized* group for the rest — so related dashboards sit together. Use **Back to dashboards** in the header to return to the list.
Some dashboards ask for a few values before they load — an **Enter parameters** prompt appears, you fill it in, and the dashboard opens scoped to what you entered. Reopen it with **Change parameters** in the header to try different values.
## The header controls
Along the top of every dashboard:
* **Date range** — scopes the whole dashboard to a window (see below).
* **Refresh** — reloads the latest data for every element on the page.
* **Export all** — downloads an Excel workbook containing every table on the dashboard, scoped to the active date range.
* **Freshness** — *Updated …* shows when the underlying data was last refreshed. Each element also carries its own freshness indicator.
## Scope by date range
The **date range** control applies to every element at once. Choose a preset:
* **All time**
* **Last 7 days**, **Last 30 days**, **Last 90 days**
* **This month**, **This year**
* **Custom range** — pick your own start and end dates.
Each element finds its own date column and keeps only the rows inside the window. Elements that have no date column are left unchanged. The selected range is kept in the page address, so a link you copy reopens with the same range.
**Trend** value cards always compare their own configured period (for example, this month versus last month) and ignore the date range control.
## Explore the data
Click a slice in a pie chart or a bar in a bar chart to **drill down**: every other element that uses the same data source narrows to that selection, so you can study one segment in context. The chart you clicked highlights your selection and offers a **Clear drill-down** action to remove it.
When a column has many categories, the smallest ones are grouped into a single **Other** slice so the chart stays readable. **Hover the Other slice** to see the categories behind it, and read each slice's value from the legend.
Open the menu on any data grid column header to **sort** (ascending or descending) or **filter** the table by that column. A default sort may have been set when the dashboard was built, which applies until you change it. Clearing your sort returns the table to no sorting.
Value cards show one headline number. A **gauge** shows progress toward a target; a **trend** card shows the change versus the previous period, with an arrow and percentage — hover the change for exactly which periods are compared.
## Export
* **Export all** (header) — every table on the dashboard, in one workbook, scoped to the active date range.
* **Export XLSX** on a single grid — just that table, with your current sorting and the active date range applied.
Set your date range before exporting — the workbook reflects whatever range is active, so it matches what you see on screen.
If a data source holds more rows than its row cap, the export covers only the captured rows and warns that it may be incomplete. Ask whoever manages that data source to raise its row cap if you need the full set.
## Keeping data current
If the numbers look out of date, check the **freshness** indicator. **Refresh** reloads the latest available data, but the underlying snapshot is only as current as the last time its [data source](/reporting/data-sources) was refreshed. If it's still stale after a refresh, ask whoever manages that data source to refresh it.
Besides *Updated …*, an element's freshness can read **Awaiting first run** (never materialized yet), **Stale** (overdue for a refresh), **Schema drift detected** (the query's columns changed at the last refresh), or **Last run failed**. For any of these, whoever manages the data source is the person to contact. An element reading **Live** draws from a parameterized data source that runs on demand, so it's always current.