Dashboard Security

When you share a dashboard, each viewer sees it through their own access policies. A regional manager sees their region’s numbers, and a department head sees their department’s, all on the same dashboard.

When the data re-runs

A viewer doesn’t always get a fresh run. Querri re-runs a dashboard’s widgets for a viewer only when the viewer has access policies that apply to the dashboard’s data, or when the dashboard has active filters.

Only widgets placed on the dashboard are re-run. Results are cached by the filters they resolved to, so viewers who end up with the same filters can reuse a result instead of waiting for a new run. While a widget is being filtered for you, it reads Applying security filters and “This may take a moment”.

Opening or viewing a dashboard isn’t written to the audit log.

Viewers with no policies

Someone with no access policies sees all of the dashboard’s data. The exception is a source that requires an access policy: without a matching policy, they see no rows from it. That setting is made through the API, not in Settings; see Sources that require a policy.

Public links

Visitors to a public link see the dashboard filtered by the policies of the person who made the link, not by any of their own. If people should see only their own slice, share the dashboard with them directly instead.

A link can also Lock current filters and Hide filter controls. See Sharing.

Dashboard filters

A dashboard filter only offers the values the viewer is allowed to see. Someone limited to one region won’t find the other regions in the list.

Who changes a filter matters. When an owner or editor picks a value, the dashboard opens with that choice for everyone. A viewer’s changes, and changes made through a share link or an embed, stay in their own browser.

Next steps

• Access Policies: the policies behind per-viewer filtering
• Filters: source filters and dashboard filters
• Sharing: share dialogs and public links