Skip to main content
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.

Full Stories reference

Creating, editing, arranging, versioning, sharing, and exporting stories

​
Why stories instead of a dashboard

​
The dashboard features you expect

Stories cover the pieces a BI dashboard is made of:
  • Live data on a schedule. A live story 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 (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 and split a report into tabs, so one story can hold several views.
  • Sharing and governance. Share a story with your whole project, specific people, or a user group; recipients always see the latest refreshed version. Admins can certify a reviewed story so readers know which reports to trust.
  • A library. The 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.