Composed dashboards

The Dashboards menu lets you compose your own views: the numbers you actually look at, laid out the way you read them. A dashboard isn’t a photograph: it keeps the question, not the answer. Open it three weeks later and it replays on the day’s data.

Note

Not to be confused with the home dashboard, which is the monitoring page STRIVN ships with. Here, you’re the one composing it.

Create a dashboard

1. Open Dashboards in the menu, then name your view.
2. Create dashboard opens the builder, empty.
3. Add widgets from the palette, or ask the assistant for them (see below).

A dashboard belongs to the team: your colleagues see it in the list and can open it.

The widgets

The palette offers seven types. The first four carry data, the last three organize the page.

Widget	What it shows
KPI	A single number — a total, an average, a latest value
Chart	A trend or a ranking
Table	One row per player, several columns
Snapshot	Frozen values, captured by the assistant at a specific moment
Heading	A subheading to separate two blocks
Divider	A horizontal rule
Note	Your own free text — a reminder, a comment

Each data widget combines a source (load, roster, injuries, GPS…) with settings specific to that source: the metric, the window, the sort order. The possible combinations aren’t the same everywhere — a source that only offers a ranking won’t offer a line chart.

You can move a widget, resize it horizontally, and delete it.

The context bar

When viewing, a bar at the top of the dashboard lets you change what you’re looking at without changing the dashboard:

• Window — last 7 days, last 4 weeks, last 12 weeks, or the season.
• Players — the whole squad, or a selection.

These settings aren’t saved with the dashboard: they apply to what you’re viewing right now. Any widget with its own window keeps it — the bar doesn’t override it.

Caution

A Snapshot widget doesn’t respond to the context bar, and that’s intentional: its values were captured on a given date. Changing the window doesn’t recompute them — it shows its capture date so the difference is visible.

What your colleagues see

A dashboard resolves for whoever is looking at it, never for whoever composed it. Two staff members opening the same dashboard won’t necessarily see the same thing: a widget whose source requires a permission your colleague doesn’t have shows up degraded, naming what’s missing, instead of showing them the numbers.

The same principle applies to a Snapshot: its values were captured with the access rights of whoever requested them. A viewer who doesn’t have those rights today sees the widget degraded, not the values.

Ask the assistant

In the builder, Ask the assistant composes the widgets for you. Describe what you want to see — “the load over the last four weeks, and the most loaded players” — and the tiles land on the canvas. You stay in control: nothing is saved until you save it.

The assistant can only compose what your team’s vocabulary allows. When a request falls outside that scope, it says so and names the setting that failed rather than guessing: a metric that doesn’t exist for your team, a window a source can’t produce.

Tip

If the assistant only proposes structure (a heading, a divider), your request wasn’t understood as a data request. Rephrase it, naming the metric and the period.

You can also compose from the chat, without going through the builder — see Composing a canvas on the fly.

Edit, delete

From the list: Open views it, Edit reopens the builder, Delete removes the dashboard for the whole team. A dashboard saved from an assistant canvas is an ordinary dashboard: it’s edited exactly like any other.