Access and Limits
AI Dashboards are experimental. You generate and refine them in the TagoIO Admin, and signed-in Run users can view them in TagoRUN. They do not support public sharing or distribution.
Use a Normal or Blueprint dashboard when you need a stable customer-facing dashboard or any of the unsupported delivery options listed below. Generation also depends on the profile AI settings, covered on this page.
Experimental status
Experimental. This feature may change or be removed.
AI Dashboard is experimental. Expect changes to:
- Prompt behavior and generated layout quality
- Admin UI (prompt bar, starters, refresh controls)
- What is supported for share, distribute, and TagoRUN
Do not treat a generated layout as a permanent contract. Prefer regenerating when the product updates.
AI availability
Generation uses the same AI path as TagoAI: profile AI must be enabled and able to serve requests.
| Requirement | Where |
|---|---|
| TagoAI / AI provider enabled | Profile Settings → Services → AI Provider |
| Credits, if generation runs on a paid model | AI Credits balance and profile spend cap |
| Monthly allowance, if generation runs on the free model | Generation counts against the profile's monthly free model allowance (TagoAI Service) |
| Own provider (optional) | Using your own AI provider; billed by that provider |
When AI is disabled on the profile, the create dialog AI tab is hidden, and existing AI Dashboards stop loading data in Admin and in TagoRUN. When AI is enabled but cannot serve requests (no credits, allowance used up, provider error):
- Generate and refine fail with the error naming the block, until AI can serve requests again.
- Existing layouts still load in the Admin; you just cannot produce a new version.
Disabling TagoAI on a profile does not delete dashboard resources. Turn AI back on and the dashboards load data again.
Who can generate
Anyone who can edit the dashboard in Admin and whose profile AI path is live can use the prompt bar. Generation runs under that profile's AI configuration and scope. There is no separate "generate without AI" path.
TagoRUN
Run users can open an AI Dashboard from the TagoRUN sidebar. The view is read-only: they see the last generated layout and its data, with no prompt bar and no way to generate, refine, or restore versions.
To let each Run user build their own version through the TagoRUN AI chat instead, turn on Per Run User Generation.
Granting access
Grant access with an Access Management policy whose Target is the Run users. The policy needs two parts:
| Permission | Rule | What it does |
|---|---|---|
| Dashboard | Access | The dashboard appears in the user's sidebar and opens. |
| Device | Dashboard access | The dashboard's queries return data from the matched devices for this user. |
| Entity | Blueprint access | Same as the Device permission, for queries that read entities. |
Grant Dashboard access on every device whose data the user should see. Deny rules override allow rules, as in every policy.
Only signed-in Run users can view AI Dashboards. The Anonymous User sees "This AI dashboard can't be shown here" instead.
What each Run user sees
Each query on the dashboard returns only rows from the devices and entities the Run user can access. One dashboard can serve several customers: each Run user sees the same layout filled with their own data.
- A widget whose devices the user cannot access shows No data. A device the user cannot access and a device that does not exist look the same.
- A query that reads several devices returns rows only from the allowed ones. A query that joins an allowed device with one the user cannot access returns no rows.
Run users have the same refresh control as Admin: the refresh button and the Auto refresh menu with Live and the intervals. Live refresh applies two rules, and they differ:
- Rows follow Dashboard access on the device and Blueprint access on the entity, and nothing else. Every reload, Live or not, returns rows only from the resources those rules allow.
- Update signals follow the stream rule: a Run user's stream on a device or entity is allowed by Dashboard access (Blueprint access for an entity) on it, or by a widget on a Normal or Blueprint dashboard the Run user has Access to that shows it. The AI or Custom Dashboard being viewed never counts, because its layout is not made of widgets the server checks.
A device shown only on the dashboard being viewed stops signaling within a minute of losing Dashboard access. No page reload is needed. The dashboard then runs a widget data reload for the widgets that read the device, the same data load the refresh button runs, and that reload carries no rows for the device.
A device the Run user keeps only through a widget on a Normal or Blueprint dashboard still signals until its next matching write or the 10-minute full data reload, whichever comes first. That data reload returns no rows for the device, because rows follow Dashboard access alone.
That reload's result no longer names the device, so the dashboard reopens its connection without it. The reopened connection runs one more full data reload when it opens. After that, writes on the device reload nothing.
Live refreshes spend the Run user's own per-minute limit on data loads (Limits and AI settings).
Device permissions limit the data that queries return, not the text in the layout. The dashboard title, widget titles, labels, units, and text blocks are visible to every Run user with Access to the dashboard. Generated text can include device names. Review the layout text before you grant access to a dashboard that covers more than one customer.
Generation does not write sampled values or value ranges into text, because those numbers would freeze at generation time. Dashboards generated before TagoRUN support keep their text until you generate again.
Limits and AI settings
- Viewing runs no AI. It spends no AI credits and does not use the monthly free model allowance.
- Data loads count toward the owner profile's data output, the same as in Admin.
- Each Run user has their own per-minute limit on data loads, so one busy user does not block the others or the owner.
- When AI is disabled for the profile, data stops loading, as in Admin, and Run users see "AI dashboards are disabled for this application".
- A dashboard that was never generated shows "This dashboard has no content yet".
TagoRUN builds the page from the dashboard's saved layout each time it opens. On dashboards generated before TagoRUN support, small layout details can differ from what you see in Admin. The content and data are the same.
Unsupported
| Area | Behavior |
|---|---|
| Share public | Not supported. |
| Distribute | Not supported. |
| Period presets | Not supported. |
| Widget grid | Not present. Unlike Normal and Blueprint, you do not place widgets on a grid. |
Use Normal or Blueprint when you need share, distribute, or a classic widget grid.
Settings that still apply
These work like other dashboard resources:
Data and usage
- Loading dashboard data counts toward normal dashboard data usage (Data Output for Dashboards).
- Generate / refine is recorded as AI usage and, on a paid model, spends AI credits (AI usage statistics).
- On the free model, each generate or refine counts toward the profile's monthly free model allowance (TagoAI Service).
- Live refresh is a data read per refresh: at most one every 5 seconds per dashboard, plus a full reload every 10 minutes (Cadence and cost).
- Interval refresh multiplies data fetches while the dashboard stays open; choose intervals deliberately.
Practical guidance
- Check the dashboard in TagoRUN with a test Run user before you grant access to customers, to confirm each one sees only their own data.
- Keep customer portals on Normal or Blueprint when you need share or distribute.
- Keep prompts and important layout notes outside the session-only chat if you need a record later (Generating and Refining).