Have the assistant build a page

When neither a widget nor a free chart can draw what you ask for, the assistant can have a made-to-measure page built: a free layout, views linked to each other, a menu to pick a match or a player, a pitch, a goal. The page opens next to the conversation and can be saved to a dashboard.

Canvas first, page second

The assistant picks its answer in this order:

a canvas of widgets (chart, figure, table);
a Free chart in that canvas, when no chart from the catalogue fits;
a page, only when neither can draw the request: a free layout, several linked views, an interaction (filter, tabs, picking a player or a match), a pitch diagram, a shot map with the pitch and the goal crossed, a timeline that mixes several kinds of events.

It also builds a page when you ask for one: “make me a page with…”. Conversely, a request the canvas can draw (a radar of two players, a ranking, a line chart) stays a canvas: if you want a page, say so, or describe the picker, tabs or layout you expect.

Examples of requests that give a page:

“A page with our latest matches: I pick a match and see its score and its goals minute by minute.”
“Two players head to head on load, minutes and distance over the last six weeks, with a menu to pick the two players.”
“Where our shots start and where they end up in the goal this season: I pick a zone on the pitch and see where those shots went.” (the same crossing as the Pitch tab)
“A tabbed view: one tab per line (defence, midfield, attack), and in each one every player’s load and wellness.”
“A season timeline that mixes matches, injuries and weekly load on the same time axis.”
“Load against wellness on the same chart, with a menu to pick the player shown.”
“A small chart per player of their week of load, all on the same scale, in a grid.”

Asking well

Say what the page should show and how you choose in it: by match, by player, by line, by period. The more precise the request, the fewer choices the assistant makes for you. If it hesitates between two readings, it asks you a question, as for any request.

A page can contain, among other things:

key figures and sortable tables;
a player picker, a match picker (the run of latest matches, with their results), tabs, a switch between two views;
a match header with its score, a match timeline minute by minute (our goals above, theirs below);
rankings, line charts, bars, donuts, a heatmap, a scatter plot, figures against their target zone;
two players (or two sides) head to head, a team line-up, the week day by day;
a pitch, a goal as the shooter sees it, or both crossed: a zone picked on one keeps on the other only what came from it or went into it.

What a page does not do — the assistant tells you before building, and offers the closest alternative (a canvas, a free chart, an aggregated read, the STRIVN screen that does it):

a form or data entry: a page saves nothing;
a dialog box, a window or a pop-up;
a file download or export (PDF, Excel, image);
live or refreshing data (during a match, every minute);
links or content from the Internet.

While it builds

The page is built in the background, usually in 20 to 90 seconds. In the conversation, a card shows its title, Building the page… and “It will open next to the conversation as soon as it is ready.”

You can keep asking other questions meanwhile, change screens or reload the page: the build carries on, and the card picks it up when you come back to the conversation.
When it’s ready, the page opens on its own next to the conversation if the assistant is open. The card becomes Page generated by the assistant: click it to reopen the page whenever you want.
One build at a time per conversation. A change requested while the page is building isn’t applied: the assistant tells you so; ask again once the page appears. If the staff already has several pages building, the assistant asks you to try again in a minute.

If the build fails

The card says why:

“The page could not be built. Trying again may work.” — with the Try again button, which asks for the same page again from the same data;
“This page can no longer be built: access to its data has changed.” — no retry possible;
“The page was not built: the request is declined for now (limit reached or service unavailable).”

A failed edit leaves the previous version in place: it is still the one your next request will edit.

What a page shows

A page draws only the figures the assistant read in the conversation, with its usual tools. They are copied at build time: the page fetches nothing else and doesn’t update on its own. Like a Snapshot widget, it’s a dated picture.

Above the page, the line Page generated by the assistant says which data it comes from and when it was captured (”… — captured on …”).
Nothing is made up: the assistant describes the page in words, without copying figures, and the page reads each value from the copied data. The names shown are the ones in that data.
Before showing it to you, STRIVN renders it as a test, on a computer screen and on a phone screen: a page that stays blank or crashes isn’t delivered.
The page shows on a white sheet, whatever the app’s theme. Its text is written in the language of whoever asked for it.

To get today’s figures, two ways: Regenerate on a dashboard view (see below), or ask the assistant again.

If the page hits a problem while displaying, a banner “Something went wrong while displaying the page.” offers Ask the assistant to fix it, which sends it the request for you. If it stops responding, “The page has stopped responding.” shows with Reload.

Editing it

Carry on in the same conversation: “add the team average”, “turn the ranking into bars”, “add a tab for the goalkeepers”. The assistant builds a new version of the conversation’s page, whether its canvas is open or closed, and re-reads the data if needed. The old version stays in the conversation, marked Previous version.

A page isn’t edited by hand: even on a dashboard, a change goes through a new version asked of the assistant.

Saving it to a dashboard

Until you save it, a page exists only in your conversation: no one else sees it. A page that is never saved is deleted 30 days after it was built.

When the page is ready, its canvas header offers:

Save — the page becomes a new dashboard, named after it, visible to the staff like any new dashboard (see Sharing a dashboard).
For a new version of a page already saved, the button becomes Replace on [the dashboard], with the line “This version will replace the page saved on the dashboard …”: the view is replaced in place, its name kept. Next to it, Save to a new dashboard keeps the old one and creates a dashboard for this one.

A version saves only once: the button then shows Saved (or View updated after a replacement), then Saved on [the dashboard] when you reopen the page. To change a page that’s already saved, ask for the change in the conversation that built it, then save the new version: it replaces the view.

In the builder, an Assistant page can be moved or removed, but not edited.

Regenerate with today’s data

Under a page’s view on a dashboard, the Regenerate button reopens the assistant with the request already written — “Rebuild the page ”…” with today’s data.” — and the chip Will replace the view ”…” above the field (Cancel to drop it). Send it: the assistant re-reads today’s data and rebuilds the same page, keeping its layout. A dated period is brought forward to the same length up to today, and the squad is today’s.

The view is replaced only when you save the new version (Replace on [the dashboard]). Until then, the old one stays in place. You can also ask for a change in the same conversation before saving.

Regenerate doesn’t appear if your team doesn’t build pages, nor on a page whose data has been removed.

What your colleagues see

On a dashboard, a page displays for every staff member who can see that dashboard, as it was built. In its place, a colleague may see:

Label	Meaning
Restricted access	The page relies on data their permissions don’t cover (injuries, for example), including data read earlier in the conversation that built it: they see the title and what they’re missing, not the page.
Data removed	A player in the page was erased from STRIVN: the page goes with them and can no longer be regenerated. Ask for a new one.
Page display is suspended	STRIVN has temporarily hidden page display: only the title remains, and the page comes back afterwards.

The assistant itself doesn’t re-read the content of a saved page: it knows its title, date and source data, and re-reads the data if it needs to talk about it.

Outside the app

Public link (The public link): if the link keeps player names, the page displays, isolated as in the app, and any links in it are neutralised. If you chose initials, the reader only sees a card with the title (in initials) and View it in STRIVN. A page built in a conversation that read medical or wellness data only appears on the link if you ticked Include medical and wellness views.
PDF and scheduled send (PDF and scheduled send): the page is never printed. In its place, a card gives its title, its source data, its capture date and View it in STRIVN.

Limits

A limited number of builds per day, for the whole team. Edits, Regenerate and failed builds count. When the limit is reached, the assistant tells you and offers a canvas or a free chart until the next day.
Data size. If a read is too heavy for a page, the assistant narrows it (a shorter period, fewer players) or aggregates it (by week, by position, the top of a ranking): nothing is cut silently.
In the app only. Pages are built in the STRIVN assistant, on a computer as on a phone. No pages over WhatsApp, nor from a connected AI (Claude, ChatGPT…), which only sees a saved page’s title, date and source data.

Privacy

The page is written by a dedicated AI model that receives neither your figures nor your players’ names: it works from the description of the request, where names are replaced by markers, and from the shape of the data, with made-up values. The real figures only join the page when it is displayed, in STRIVN. The page runs isolated: it has no access to your session, your account or the Internet.