Reports
One written page that answers a question, kept and shared like a dashboard.
A report is one page, written. It answers a question about your data in sentences, with figures where a number needs one, and it is kept so the answer can be read again and shared.
When to pick one
Pick a report when you want an answer rather than somewhere to look: how last quarter went, what changed after a release, what a dataset says about a question. If you will return to the same view as the data moves, a dashboard fits better. If people will enter or change records, build an app.
Build one
From Create
Open Create, set the picker under the prompt to Report, pick the datasets it should read, and write the question. Leave it on Auto and Flitch reads the request and picks for you. See Create.
A report is one page, so the options have no page count or navigation to set. Theme and the rest work as they do for a dashboard.
Or from the chat
Ask for it in Chat. The assistant writes it in the thread, and a card follows it until it is ready to open.
A report is written by the same AI loop that edits dashboards, so you watch it being written in the editor's chat, and can stop it or come back to it the same way.
What it shares with dashboards
A report is edited and shared exactly like a dashboard:
- Editing: ask for a change in the chat sidebar, or use the inspector. See Update.
- Versions: each change is a version you can restore.
- Publishing: the same visibility options, the same
view.flitch.iolink, and the same exports. See Publishing. - Library: it sits in the Library beside everything else your space has built, and can join a collection.
A report is not fixed at one page for good. Ask for more pages, charts or an input table and it grows like any dashboard.