> For the complete documentation index, see [llms.txt](https://documentation.astera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.astera.com/astera-studio/chat/dashboards-from-chat.md).

# Dashboards from Chat

A **Dashboard** in Astera Studio is a saved layout of charts, KPIs, and tiles built on top of your data. You can build one from scratch in the Dashboard editor — or, more commonly, ask the AI in chat to build one for you. Chat is the fastest way from *'I need a Q3 sales view'* to a saved, shareable Dashboard artifact.

In this article, we will learn how to ask chat to create a Dashboard, what the generated result looks like, how to refine and re-generate the Dashboard, how to save it to your workspace, and how to share it with other people in your organisation.

## Creating a Dashboard from Chat

Dashboards work best when the AI has the source data on hand. Attach the Source File or Database Connection first, then describe what you want to see.

1. In a new or existing chat, attach one or more data references using *+* or *@*-mentions. Typical sources: a CSV in Source Files, a Database Connection, or an existing Dataprep that already cleans the data.
2. Type your request in plain language. Be specific about the shape — *Build a dashboard showing top 10 customers by sales, sales by segment as a donut chart, and a KPI card for total revenue and total profit.'*

![](/files/8ebb2fd9b6eba4979d0dba1104763927730fd774)

3. Send the message. A task tracker appears showing the AI's plan.

![](/files/f8e05ec46b80a5775055a5f0c3a1534273d53b40)

4. When the tracker reaches *DONE* the out panel shows you the full-created dashboard.

![](/files/7f16eb63febca6eba72542a5085289c30ae3b2d0)

{% hint style="info" %}
**Tip:** vague prompts produce vague dashboards. Tell the AI what charts you want. The clearer the spec, the closer the first draft will be to what you want.
{% endhint %}

## Saving the Dashboard to the Workspace

A Generated Result lives in the chat. To keep the Dashboard around — so you can *@*-mention it later, share it through the Catalog, or schedule a refresh through an Automation — save it into the workspace's **Dashboards** category.

![](/files/1c17ebc398800e25065707698d02c1285011a773)

## Sharing the Dashboard

Once a Dashboard is in your workspace, you can share it with your colleagues. One important thing to note is that for any asset to be shareable or accessible to other users, it must first be published to the catalog. The catalog is where all shared assets become accessible across teams.

![](/files/9643a45b3e5a6df58980102a30d631194180a4c2)

Once published, you can simply copy the link and share it with anyone.

![](/files/ace8dbca80f8d18568e47c7c00c4051b72a6097d)

You can also preview the shared link, where you’ll see the complete dashboard along with an attached chat interface that allows users to ask questions directly about the dashboard

![](/files/b958579d9e37b5c26450b6eebc49d693b07babaf)

![](/files/ebffc0266250ec6fec73169c66e5e4598f6867a3)

## Keeping the Dashboard Fresh

Most Dashboards are built from live sources. By default, the dashboard is refreshed every two hours. If you want to refresh more frequently you can use two patterns to keep them up to date:

* **Manual refresh** — open the Dashboard from the workspace and click *Refresh* in the editor's toolbar. The underlying queries re-run.,

![](/files/505e231605d158ad760eddec303c231c1d6f2ffd)

* **Scheduled refresh** — set up an Automation in the Automations module on your desired trigger or event. Run it on a schedule (every morning at 8 AM, every Monday, etc.) so viewers always see fresh numbers without thinking about it.

![](/files/cbc445ae0e619bee10575ff21549ba049ad2d240)

![](/files/0b1c69382e09b7d3b4532bd3ec3d65b8b5f7f72d)

## Conclusion

To conclude, this is how you go from a chat request to a saved, shareable Dashboard in Astera Studio. Attach the data, describe the layout, refine until it's right, save to the workspace, and publish to the Catalog when you're ready for the rest of your organisation to see it.


---

# 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://documentation.astera.com/astera-studio/chat/dashboards-from-chat.md?ask=<question>&goal=<endgoal>
```

`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.