> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getnao.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Stories

> How stories and live stories replace your BI dashboards

Most BI tools do two jobs: they turn questions into charts, and they keep those charts up to date on a dashboard. nao covers both from the chat interface, without a separate modelling layer or dashboard builder. **Stories** are the nao answer to the BI dashboard.

A story is a persistent, shareable report built from a chat analysis: narrative text, live charts, and tables in one document. Instead of dragging fields onto a canvas, you ask the agent in plain English and refine from there.

<Card title="Full Stories reference" icon="book-open" href="/nao-agent/chat/capabilities/stories">
  Creating, editing, arranging, versioning, sharing, and exporting stories
</Card>

## Why stories instead of a dashboard

| BI dashboard | nao story |
| - | - |
| Build charts by hand in a drag-and-drop editor | Ask in plain English, the agent writes the SQL and the charts |
| A separate tool to learn and maintain | Lives in the chat, next to the analysis that produced it |
| The query behind a tile is often hidden | Every chart shows its SQL and underlying data |
| Dashboards drift from the questions people actually ask | Stories start from real questions and keep the thread |

## The dashboard features you expect

Stories cover the pieces a BI dashboard is made of:

* **Live data on a schedule.** A [live story](/nao-agent/chat/capabilities/stories#live-stories) stays connected to its queries and refreshes on a cadence you choose (every few minutes, hourly, daily, or a custom schedule), so the numbers are current without anyone rebuilding the report. It can also regenerate the narrative so the commentary matches the new data.
* **Self-serve filters.** Add [filters](/nao-agent/chat/capabilities/stories#filters) (dropdowns, search, date ranges) so a reader can slice the report without editing it, the same way they would change a dashboard's filter bar.
* **Layout.** Arrange charts and tables into [grids](/nao-agent/chat/capabilities/stories#arranging-charts-into-a-grid) and split a report into [tabs](/nao-agent/chat/capabilities/stories#tabs), so one story can hold several views.
* **Sharing and governance.** [Share](/nao-agent/chat/capabilities/stories#sharing-a-story) a story with your whole project, specific people, or a [user group](/nao-agent/chat/admin/user-groups); recipients always see the latest refreshed version. Admins can [certify](/nao-agent/chat/capabilities/stories#certified-stories) a reviewed story so readers know which reports to trust.
* **A library.** The [Stories Library](/nao-agent/chat/capabilities/stories#stories-library) organizes reports into folders, favorites, and pinned items, the way a BI workspace organizes dashboards.

## Bringing an existing BI tool across

Already have dashboards in Metabase or Tableau? nao can migrate them into stories so you don't start from a blank page. See [Migrate your BI to nao](/nao-agent/chat/bi/migrate-bi).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.