Dashboards
Charts and key figures from tables and workflows, filters, buttons, presenting and sharing.
Your first dashboard from a table
A dashboard shows at a glance what your workflows and tables produce: key figures, charts and tables on a grid. You build it the way you will see it: tiles from the palette onto the grid, and per tile you choose in plain words where the data comes from and what you want to see. Here you make a sales overview of a table of orders.
Filters and the time picker
A dashboard only becomes really useful when you can zoom in: only this week, only this customer, only the big orders. Every dashboard has a bar at the top for that: the time picker on the right, the builder's filters on the left, and ＋ Filter for any field. A click on a bar filters the other tiles. Everything you choose is in the address, and what you need often you keep as a view.
Present and share
A dashboard is for looking at together. Present puts it full screen, without buttons for editing, and refreshes by itself: good for a screen on the wall. You can share with your colleagues (signed in, always live data) or with anyone who has the link (no sign-in, a snapshot). A link can expire and you revoke it with one click.
Signing in on your company's Flow address
Your colleagues never need to see the portal. Every environment has an address of its own with a sign-in page in your company's house style. Whoever has a work account signs in through the company's sign-in system (such as Entra ID) and lands on the home straight away; whoever builds signs in with password and code and lands in the studio, one click away from the home.
A colleague's day: home, dashboard, chat and feedback
This is how a colleague uses the home: a quick look in the morning at how the week is going, a question to the HR colleague, and when something is not right, feedback — with a screenshot on which they point out what is wrong and black out what nobody needs to see. The reply comes back in the home.
Buttons that run workflows
A dashboard is not only for looking. A button starts a workflow: enter an order, make a report, fetch data again. The button can ask a few questions first and ask for confirmation; then you watch the run happen live and the tiles refresh. A table can have an action on every row, with that row as input.
Searching knowledge bases from a dashboard
Next to the figures you sometimes want the answer to a question straight away: how to adjust the brakes, what the contract says. A search tile searches by meaning in the knowledge bases you choose and shows the best matching parts, with the document they come from. Bind it to a search text in the filter bar, and it searches along with what you type there.
Showing browser-step screenshots to the person who starts the workflow
A workflow with browser steps operates a website like a person. Whoever starts it with a button on a dashboard or through an AI Colleague in the chat wants to see what happened. Switch on ‘Show screenshots to the person who starts it’ in the browser session: the screenshots then appear in the editor per step, live under the button, on a tile and under the answer in the chat. Only the person who started the run sees them, never through an open link, and every time someone looks at one, it is in the audit log.
Keeping a dashboard together
Two people on one dashboard works well when you see what the other does. When a colleague saves the dashboard while you have it open, it says so at the top at once. When you then press Publish, your colleague's work does not go live unseen: Flow asks you to open the new version and look at it first. When a colleague publishes or shares, that is said in those words too. And the tiles follow their data: when someone adds an order, your dashboard counts it at once.
Answering feedback
Colleagues give feedback from the home: a thumb on an AI Colleague's answer, or through the Feedback tab with a screenshot on which they mark something and black out what must not be sent. In the studio you read it all in the Feedback inbox, reply (the reply reaches the colleague in their home, never by mail), keep the status up to date and turn a bad chat answer into a test case, so it does not happen again.
Building the home for your colleagues
The home is what everyone in your company sees at your Flow's address: a welcome, announcements, the figures that matter and a question box for the AI Colleagues. You build it in the studio like a dashboard, with a variant per audience. Before you publish, you view it as that audience and Flow checks you do not open up anything that should stay closed.
Navigation per role: the side menu and the tabs
Everyone gets the menu that fits their work. Per audience you put together the side menu — with icons, groups and submenus — and the tabs above the page. Here the bakery's managers get a group Management with the revenue per shop, which employees do not see. Hiding is a convenience, not security: whatever a person may not open, the server always refuses.
Building information pages with blocks
Besides the start page, the home can have pages that explain: for new colleagues, a way of working or a project. You build them from blocks that are designed with care — a hero, cards, steps, a video, frequently asked questions, a callout and contact people — and fill them in Dutch and English. Then you put the page in the menu.
The house style: logo, type and colours
What your colleagues see wears your company's house style: the sign-in page, the home, the dashboards and the chat in it. You upload the logo, choose the type and the colours, and Flow checks that everything stays readable — also for colour-blind readers. A colour that is not readable enough is refused, with one that does work beside it. The studio keeps Flow's own look.
The home together
When two people build the home, publishing never goes over the other's work: when a colleague saved the home after you opened it, Flow asks you to open that version first. And colleagues reading the home at that moment calmly see that there is a new version; they choose when to look at it, the page never jumps under their eyes.
Let Claude Desktop build your home
With MCP access an AI app such as Claude Desktop builds the home for you: it starts from one of Flow's well-composed examples, sets the house style and the logo, lays out the tiles, has the security check done and publishes. It acts as you and can never do more than your role; changing rights and accepting a risk remain work for people.