Build · Design
Design a New Dashboard with AI
Pick a published datasource, and a design Project, then design through conversation. AI designs the iterations as you, the Tableau Creator in your Tableau Cloud.
Platform guarantee
Every figure on a designed dashboard is real.
Before each design turn, TabTotal queries your own session for a live data profile, and every quantity comes from it. If your connection cannot answer, the preview is labelled as placeholders and says why.
In the product
Build, as it actually looks.
The register
What Build does for you.
Every line below was read out of the product’s own source on 14 August 2026.
Full data validation against live Tableau Cloud data: every zone is re-queried on your own session and the result is printed as design value beside live value.
The board states its own coverage: how many zones were checked against live data and how many could not be, named individually rather than left implied.
The model authors a spec. The workbook bytes come only from the deterministic emitter, which the AI never touches.
Every quantity is grounded in a live query on your own session. The prompt forbids inventing one: if the site holds 4 users, the dashboard shows 4.
When no live data answers, the server says so and the preview is labelled as placeholders. It never disguises them.
Publishing is dual-authorized: an approve flag plus a re-typed signature, and it always creates a new workbook, never an overwrite.
A render that lands outside the project you chose is moved back into it, and the response names where it actually went.
1,112 automated tests are defined in this app’s own source code, and CI runs every one of them before a release ships.
Specification
- Version1.45.1
Shipping at the 24 August 2026 research pass.
- Packageboreon-tabbuild
The repository this behaviour lives in. Every claim above has somewhere to be checked.
- Model useOptional, on your own key
Switched on by you, running on the provider key you supply.
Assurance
The AI is yours to switch on.
Where Build uses AI, it runs on the provider key you supply. Your prompts go to the provider you picked, and nowhere else.
The model drafts. Anything that would change your Tableau content arrives as a card that routes into the same approval gate a person would use, with the same signature and dual-control rules you already run. Your team keeps the pen.
Design
Describe what you want, or bring a file you already have, and get governed content back.
Build sits with these, and one login opens all of them with your Tableau permissions.
See Build in your own Tableau Environment.
A month on your own content is a better test than any description of it.