Dashboards

A dashboard is a set of visuals that track the KPIs you want to watch over time. Where a conversation is for asking and analyzing, a dashboard is for tracking and monitoring — the handful of numbers you check on a regular cadence.

Like everything else in Streya, a dashboard is built by prompting the agent, not assembled by hand. You describe the visual you want and the agent adds it; you describe a change and the agent makes it.

How a dashboard is structured

A dashboard is made of three building blocks:

• Slicers: interactive controls that filter the dashboard: a date range, a region, a segment. Move a slicer and every widget that responds to it updates together.
• Tabs: dashboards are organized into tabs, so you can group related widgets instead of crowding everything onto one screen — an overview tab, a sales tab, an accounts tab.
• Widgets: the individual visuals on the dashboard: cards, charts, and tables. A widget is one visual placed on the canvas.

Build and View modes

A dashboard has two modes:

• Build mode — where you create and edit. You work with the Author, an agent specialized in crafting dashboards: describe what you want and it adds tabs, widgets, and slicers, which you can then arrange.
• View mode — where you read and share. Open a tab, move the slicers, read the charts. This is the mode the rest of your team uses day to day.

Today you start a dashboard from scratch in Build mode with the Author. You can’t yet begin one from an existing conversation — that analysis has to be recreated in the dashboard.

Be specific

The Author works from your description, so the detail you give shapes what you get back. A generic prompt produces a generic dashboard:

Build a sales dashboard.

That returns something reasonable but standard — whatever a “sales dashboard” usually means. It’s a fine place to start: begin broad and refine as you go, the same way you would in a conversation. But you’ll reach what you actually want faster by being specific from the start.

To be specific, name:

• The KPIs — by their names in your model: net revenue, new customers, win rate.
• Time frames and comparisons — this quarter versus last, the last 24 months, versus target.
• Breakdowns — by product category, by region.
• How to organize it — which tabs, and which slicers to add.
• The visual type, where it matters — as a card, as a table (see Visuals for what each type can do).

Put together, a specific prompt looks like:

Build a sales dashboard with three tabs. An overview tab with cards for net revenue, new customers, and win rate, each versus last quarter. A trends tab with monthly revenue by product category over the last two years. An accounts tab with a table of the top 20 declining accounts. Add a date-range slicer and a region slicer.

Select a widget to talk about it

When you want to change one specific widget, click it to select it first. That tells the Author which widget you mean, so your instruction can stay short:

(revenue card selected) Compare against the same quarter last year instead.

(trends chart selected) Make this a stacked bar and show only the top 5 categories.

With nothing selected, name the widget in your prompt — “the revenue card”, “the accounts table” — so there’s no ambiguity about what to change.