From 4f94a4c4952c0491a9812e16fce035c7aa0cf581 Mon Sep 17 00:00:00 2001 From: Mohit Nain Date: Fri, 14 Feb 2020 00:04:58 +0530 Subject: [PATCH] Docs: Update phrasing line 35 (#22152) Idea is to provide information to the user that query can be executed on any data source that is available in grafana, therefore suggested little modification --- docs/sources/installation/security.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sources/installation/security.md b/docs/sources/installation/security.md index 281b173fa33..344e2ddd9cf 100644 --- a/docs/sources/installation/security.md +++ b/docs/sources/installation/security.md @@ -32,7 +32,7 @@ Require all network requests being made by Grafana to go through a proxy server. ## Limit Viewer query permissions -Users with the Viewer role can enter *any possible query* in *all* data sources available in the **organization**, not just the queries that are defined on the dashboards for which the user has Viewer permissions. +Users with the Viewer role can enter *any possible query* in *any* of the data sources available in the **organization**, not just the queries that are defined on the dashboards for which the user has Viewer permissions. **For example:** In a Grafana instance with one data source, one dashboard, and one panel that has one query defined, you might assume that a Viewer can only see the result of the query defined in that panel. Actually, the Viewer has access to send any query to the data source. With a command-line tool like curl (there are lots of tools for this), the Viewer can make their own query to the data source and potentially access sensitive data.