Appearance
Reports
A report is one chart with one query. You pick the data, you pick the chart type, you save it. Open it later, share it with a colleague, drop it onto a dashboard. The report owns its own date range and filters — the dashboard just embeds it.
This is the surface for ad-hoc analysis. Build, iterate, save when it stops being throwaway.
What a report is
| Property | Description |
|---|---|
title | Display name. |
description | What question this report answers. |
chartType | One of stackedArea, line, pie, stackedBar, groupedBar, donut, heatmap, waterfall, scatter, horizontalBar, multiLine, wholeNumber. |
query | The underlying data query — what you are measuring, sliced how. |
visibility | private (only you), shared (anyone in your org). |
dashboardId | The dashboard this report is pinned to, if any. |
The catalog
Workforce Analytics → Reports → Catalog is a library of pre-built report templates — common questions Flowstate customers ask, packaged so you can clone, tweak and save without starting from scratch. Things like "headcount by team this quarter", "FTE allocated to compliance work", "vacancy fill rate by geography".
The catalog is a starting point. Clone a template, point it at your data, save as your own.
Building a new report
Reports → New report opens the builder:
- Pick a metric (headcount, FTE, cost, allocation, effort).
- Pick a slice (by team, by project, by driver, by cost centre, by geography, by job role).
- Pick a date range.
- Pick a chart type.
- Save with a title.
The preview updates as you change inputs. Save when you are happy.
Filtering, sorting, sharing
The list view supports filtering by visibility (mine, shared), chart type, owner (me, others), and whether the report is on a dashboard. Sort by last updated, title, or chart type.
Visibility works the same way as on dashboards — shared reports are visible to anyone in your org with permission to see the underlying data. Cells they cannot see render as permission-required placeholders.
TIP
Use private while iterating, flip to shared once it is presentable. Sharing half-built charts is how dashboards become noise.
Pinning to a dashboard
Each card has an Add to dashboard action that lists your dashboards. Pick one and the chart becomes a card on that dashboard, in addition to remaining accessible on its own URL. Removing it from a dashboard does not delete the underlying report.
A single report can be on multiple dashboards. Edit the source and every dashboard that embeds it picks up the change.
Date ranges and scenarios
Like dashboards, reports inherit the active scenario context. Open one inside a scenario and the chart re-renders with the scenario's changes. The saved date range is the default — you can override it per-session via the chart's date range control without changing the saved value.
Where to go next
- Dashboards — collect charts into a saved view.
- Strategy view — pre-built strategic charts you can clone.
- Financial view — pre-built financial charts you can clone.