Skip to main content

AI Dashboard Access and Limits

Use this page as your checklist before you share an AI Dashboard. It covers turning AI on for the profile, the Access Management permissions your Run users and Analyses need, what happens when you change that access, and how generation counts toward your quotas.

For prompting and generator rules, see Generating AI Dashboards with Prompts. For how each Run user gets their own dashboard, see Personal AI Dashboards for Run users.

AI availability​

Generation uses the same AI path as TagoAI: profile AI must be enabled and able to serve requests.

RequirementWhere
TagoAI / AI provider enabledProfile Settings → Services → AI Provider
Credits, if generation runs on a paid modelAI Credits balance and profile spend cap
Monthly allowance, if generation runs on the free modelGeneration 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, you can't create new AI Dashboards, because the AI Generated option no longer appears when you create a dashboard. Existing AI Dashboards also stop loading data in Admin and in TagoRUN, where Run users see "AI dashboards are disabled for this application".

Disabling TagoAI on a profile does not delete dashboard resources. Turn AI back on and the dashboards load data again.

When AI is enabled but can't serve requests (no credits, allowance used up, provider error), generate and refine fail, and the prompt bar names what blocked them. See Troubleshooting. Existing layouts still load with their data.

Permissions for Run users​

Set these in an Access Management policy whose Target is the Run users. Defining Permissions describes each rule.

Seven grants a Run user needs: AI Chat on for the portal, Dashboard Access, Dashboard AI dashboard generation, AI Access, Device Dashboard access, and, often missed, AI Read device data with Device AI access so the chat can look up the devices.

View the dashboard​

PermissionRuleWhat it does
DashboardAccessThe dashboard appears in the user's sidebar and opens.
DeviceDashboard accessThe dashboard's queries return data from the matched devices for this user. Grant it on every device whose data the user should see.
EntityBlueprint accessSame as Device → Dashboard access, for queries that read entities.

Only signed-in Run users can view AI Dashboards: the Anonymous User sees "This AI dashboard can't be shown here". Check the dashboard with a test Run user before you grant access to customers, to confirm that each one sees only their own data.

Edit a personal dashboard​

In Admin, anyone who can edit the dashboard can use the prompt bar or the AI chat. In TagoRUN, first turn on AI Chat in the TagoRUN settings, under TagoRUN → AI. This setting enables both the prompt bar and the AI Chat in the portal. See Enable and test AI Chat. Then, on top of the view permissions above, a Run user needs two permissions in an Access Management policy that targets them:

PermissionWhat it does
Dashboard → AI dashboard generationLets the user change their personal dashboard: prompt, restore, and reset. Grant it on each AI Dashboard they may change.
AI → AccessLets the user use AI in the portal. Without it, the prompt bar and the AI Chat don't work for them, even with AI dashboard generation.

A user without AI dashboard generation only views. The permissions apply the same way whether the Personalized dashboards setting is on or off.

For the AI Chat to look up the user's devices, also grant AI → Read device data and Device → AI access on the same devices. The prompt bar does not need them. See Allow access to application data.

Data and text visibility​

Each query on the dashboard returns only rows from the devices and entities the Run user can access. A widget whose devices the user can't access shows No data in this range, the same as for a device that does not exist. A query that joins an allowed device with one the user can't access returns no rows.

Text on the dashboard is visible to every viewer

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, and generated text can include device names. Review the layout text before you grant access to a dashboard that covers more than one customer. With the Personalized dashboards setting on, Run users never see the main dashboard.

Generation does not write sampled values or value ranges into text, because those numbers would freeze at generation time.

Permissions for an Analysis​

An Analysis calls the AI Dashboard routes with the token it receives when it runs, context.token, as is. Its Access Management policy must grant the matching Dashboard rule on the dashboard. See Dashboards for analysis Targets.

RequestDashboard rule the Analysis needs
Create Dashboard with "type": "ai"Create
Edit Dashboard (per_user, ai_instructions)Edit
Generate AI DashboardEdit
List Run Users of an AI DashboardAccess
List Dashboard Versions with run_userAccess
Restore Dashboard Version with run_userEdit
Reset an AI Dashboard CopyEdit

Without the rule, the request is refused with "Authorization denied". The Analysis does not need AI dashboard generation: that rule is for Run users. For the steps, see Build dashboards with an Analysis.

When access changes​

  • Dashboard → Access removed. The user can't open, load, or prompt on the dashboard, and leaves the User picker.
  • Device → Dashboard access removed. The user stops getting that device's data. New readings stop arriving within a minute, or within 10 minutes if the user still sees the device on a Normal or Blueprint dashboard. Rows already shown drop out the next time the widgets reload. Device names already written into titles or text stay until the dashboard is generated again.
  • AI dashboard generation removed. The user can't change, restore, or reset their personal dashboard, but keeps seeing it. Reset it for them to return them to where users without one start.
  • Run user deleted. Their personal dashboards are deleted with them.
  • AI Dashboard deleted. Every personal dashboard is deleted with it.
  • AI Dashboard duplicated. The duplicate keeps the Personalized dashboards setting and the rules. Personal dashboards are not duplicated.

Quotas and billing​

  • Viewing runs no AI. It spends no AI credits and does not use the monthly free model allowance.
  • Paid models. Each generation spends AI credits and follows the profile's billing mode and spend cap, whoever starts it. Each one is recorded as AI usage (AI usage statistics).
  • Free model. A generation you or an Analysis start counts toward the profile's Admin requests allowance. A Run user's generation counts toward TagoRUN AI requests, which is separate. A prompt from the prompt bar counts once. A chat turn that changes the dashboard counts twice, once for the turn and once for the generation. A question counts once. Restoring and resetting start no generation. See TagoAI Service.
  • Concurrency. One generation, restore, or reset runs at a time on each dashboard or personal dashboard, and at most three generations run at once per profile. Extra requests are refused until one finishes.
  • Data loads. Loading data counts toward the profile's data output, the same in Admin and TagoRUN (Data Output for Dashboards). Each Run user has their own per-minute limit on data loads, so one busy user does not block the others or you. Live updates spend that limit.

Unsupported​

AreaBehavior
Share publicNot supported.
DistributeNot supported.
EmbedNot supported.
Widget gridNot present. Unlike Normal and Blueprint, you do not place widgets on a grid.

Use Normal or Blueprint when you need share, distribute, Embed, or a classic widget grid.