Portal · Orchestrate
Explore Tableau using AI
Browse every project, workbook and data source on the connected site, then ask the AI Agent about whatever you are looking at.
Platform guarantee
Your data is the only thing the AI can reach.
The AI works inside a database engine started with external access switched off. It reads the data you gave it and nothing else on the machine. The boundary is the engine itself, not a list of words to watch for. How a question is phrased makes no difference to it.
In the product
Portal, as it actually looks.
The register
What Portal does for you.
Every line below was read out of the product’s own source on 14 August 2026.
Read-only by construction: the transport contains no publish, update or delete method at all.
Its own words: Portal browses your Tableau site over the REST API and never changes anything.
An embedded interactive viewer, signed by a per-domain Connected App, where no token ever reaches the endpoint.
Data-source deep dives show custom SQL verbatim and a live row preview.
The Agent answers beside the live dashboard, and it shows its receipts: the corpus rows it loaded, the site it read on screen, the live server statistics it pulled, and every query it ran with the rows returned and the milliseconds it took.
Those reads run against your Enterprise Semantic Layer and your own site, so a leadership answer arrives with the numbers already reconciled to the governed source rather than retyped from it.
Specification
- Version0.25.2
Shipping at the 24 August 2026 research pass.
- Packageboreon-tabportal
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 Portal 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.
Orchestrate
Trace what feeds what, watch how it runs, and put the right view in front of the right people.
Portal sits with these, and one login opens all of them with your Tableau permissions.
See Portal in your own Tableau Environment.
A month on your own content is a better test than any description of it.