> ## Documentation Index > Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt > Use this file to discover all available pages before exploring further. # Dashboards (Beta) > Ask the Neo Support Agent for a dashboard of your data: it writes the code once, and the page shows the numbers until you refresh them Dashboards are in **Beta**. They are free, and a dashboard refreshes only when you ask it to. A dashboard is a page of widgets: headline numbers, tables, charts, and optionally a written summary. You describe it in a chat with the **Neo Support Agent**; it writes a small program for each widget that reads your systems, and the layout that draws it. From then on no AI runs unless a widget's code asks for it: every refresh runs those programs again, rather than asking a model to read your data afresh. A summary widget can ask for one, in which case its wording varies between refreshes. A dashboard is not an agent and not a workflow. It has no schedule, no runs in **Executions**, and it costs no credits. ## Building one Building a dashboard is for admins of your workspace: its code reads your whole workspace's data. Open [**Dashboards**](https://dashboard.neoagent.io/dashboards) and click **New dashboard** (admins see it when the workspace has the Neo Support Agent). The Neo Support Agent chat opens beside an empty page; ask for the dashboard you want. A pasted spreadsheet, CSV or example report is the best starting input. The agent asks at most a question or two (who reads it, where the data comes from), decides the rest itself, and lists its assumptions so you can correct any. Each time it writes the dashboard, every widget runs against your live data and the agent reads the first rows back. A widget that could not get its data says why, and the agent fixes it before it goes on. The dashboard appears beside the chat as it is built. To change it later, an admin opens the dashboard and clicks **Adjust with Neo**: a Neo Support chat opens beside it with the dashboard already named, and the page updates as the agent writes. Every version of the widgets is kept, so Neo can also restore an earlier one; a change to the name, period or permissions is not a version. An admin can also ask the agent to build, read, refresh and delete dashboards from any other Neo Support conversation, through the [Neo API](/agents/tools/management/neo-api); the card it posts opens the dashboard. In the chat, dashboards are for admins only: for other members the agent cannot open them, and they view and refresh dashboards on the page. Every call a dashboard makes is read-only, under the integration permissions the agent chose for it: it cannot change anything in your systems. ## Viewing and refreshing Open **Dashboards** in the sidebar and click one. The header says when the newest widget was read ("updated 4 minutes ago"), or **never refreshed**. Each widget shows its data and the time it was read. Opening the page does not refresh anything, the same way Grafana works: * **Refresh** reads every widget again now, over the dashboard's period as of now. While it runs the button spins and the widgets keep their last data. A widget is skipped when the refresh that last wrote it started less than a minute ago. * Each widget has its own refresh button, with the same one-minute cooldown. * **Auto-refresh** (Off, 5m, 15m, 30m, 1h) refreshes the page on that interval while it is open, counting from when you pick it. A refresh you start yourself does not move the next one. It is a setting of your browser, remembered per dashboard, and it pauses while the tab is hidden: a refresh that came due while you were away runs when you come back. * A widget read more than 15 minutes ago, or before the dashboard last changed, shows its time in amber, whether or not its last refresh failed. * A widget whose last refresh failed keeps showing its last good data, marked **refresh failed**; one that never got data is marked **failed**. Click the mark for the reason in one sentence. If the reason is a missing permission group, an admin can ask Neo to add it to the dashboard. The dashboard's creator and admins also see **Details**, the full error Neo uses to fix the widget. The page hides it from other members only: anyone who reads the dashboard through the API gets the full error. * A widget that has never been read says so and asks for a refresh. ## Period Every widget reads one data window, the dashboard's **period**: the last N days, the previous calendar week, or the month to date, in a timezone you choose. It is evaluated at every refresh. An admin can tell the agent to change it. ## Who can see and change a dashboard Every member of your workspace who can sign in sees every dashboard and can refresh it on the page. Only an admin builds one or changes its widgets or the integration permissions it reads with, and only an admin can ask the agent to rename it or change its period. The person who built it, or an admin, can delete it. Deleting a dashboard through the agent always asks for your approval first; from the list, the bin icon shows only to those who may delete. ## What is coming Schedules, delivery by email and Teams, stored history for trend widgets, and sharing per dashboard are planned for a later version. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.