Hi there, I am trying to use Grafana for SaaS product with PostGreSQL. I am filtering my queries based on two parameters, currently any user who comes to Grafana is able to edit the parameter value and see other’s data hence they can access database. Is there any in-built option available which can restrict user’s to access other user’s rows based on a field, bascially RLS? And role/role_mapping like Kibana does? If not, is there any way community recommends/adopts for this?
If OSS/Cloud/Enterprise any can help I can consider it. Currently I am on OSS/Cloud.
which parameter value are they able to edit? and what do you mean by that?
Grafana doesn’t provide built-in row-level security for SQL data sources. Grafana roles and permissions don’t provide automatic row-level filtering for SQL data sources. Dashboard variables are not a security boundary, so you shouldn’t rely on them to prevent users who can modify variables or queries from accessing other rows.
As you are using PostgreSQL, the recommended approach is to enforce row-level access in PostgreSQL itself using Row-Level Security (RLS) policies (or expose only restricted views if appropriate). Grafana will only receive the rows the database allows.
Grafana Enterprise adds features such as data source permissions, but it does not replace database-level RLS for per-row access control.