Thanks for the quick reply! Ah, so you’re saying create each user in their own organization (I can do this by basing the AuthProxy on the email, rather than at present where I deliberately base it on a fixed username). I’ll play with this configuration, although given that the orgId is also in the URL, I guess a curious user can just select another orgId, and hence still see the data for another user, circumventing the SQL permissions?
I also came across this link, Grafana templating by logged in user. I hadn’t thought about using dashboard folders. Could these help for my use case?
My fallback is to use our SimpleJson datasource for everything since this is served by a Golang backend where we can use the user ApiKey passed in a HTTP header to differentiate the users, and then make Postgres SQL queries within Go code. It would be so much nicer though to write the SQL queries in the Grafana Postgres datasource