Possibility to disable refreshes on Dashboards

we can think of it like a “Read-only” Dashboard.

The idea aims to prevent users from triggering query runs from the dashboard.

Sometimes you have some queries with long run-times. Although it’s nice to have the flexibility of refreshing right away from the dashboard, it can be annoying for the user to trigger an update and need to wait for a long time.

Hello wesley,

not sure what you mean. When you publish a dashboard and share the link with the users, they can not refresh by themselves. It is read only for them.
As a creator you can refresh it when they ask for it, OR you schedule the refresh on the query page lower left says ‘refresh schedule’ by default Never

Hope you can continue with your idea


Since V8 this is no longer true. From our documentation:

To force a refresh, click the Refresh button on the upper-right of the dashboard editor. This runs all the dashboard queries and updates its visualizations.

In V7 and earlier visitors to a public dashboard could not refresh it.

That’s not the use case OP is asking about. OP is referring to logged-in users. Right now, if a logged in user can see a dashboard then they can refresh its visualizations. The feature request is for a way to disable this on a per-dashboard basis.

1 Like

Exactly, @susodapop.

Adding more details about the use case, our dashboard has parameters and when the user opened the dashboard for the first time in the day, it would trigger the query execution.

We managed the situation by:

  1. splitting/duplicating the original query into 3 others (Daily, Weekly, Monthly), with slight changes on the underlying queries. These queries has their own refresh schedule.
  2. The altermost query (the one that will have the widgets for the dashboard) uses the query results as data source, cached_query_672, for instance.

we lost a bit of flexibility on the parameters but kind of achieved what we wanted.

sorry for the late update on this.

1 Like