Card #3630 · Grafana
Lack of user-based data access control and session limits
Users are struggling with the inability to restrict data visibility based on the logged-in user's identity, often requiring external proxies or database security. Additionally, there is a need to limit concurrent user sessions to prevent high memory consumption and system load.
Pain score
0.15/ 1.00 · weighted product of four components
Reach0.63distinct authors (log-normalized)
Recency1.00freshness decay, half-life months
Engagement0.12upvotes + comments, normalized
Monetization0.50willingness-to-pay cues in evidence
§ Evidence — 3 verified quotes
I want to create a table where, if a given user logs into system, the table should only show the document fields that where the logged in user id is tagged in user_email field.
grafana offers nothing in the form of data source protection. Proxies or database security is needed to prevent accessing unauthorized data.
Query is how to limit number of concurrent user logged into grafana?
Comments are a Pro feature — join the conversation, share what you've shipped, hear what others are building.
Upgrade to Pro