Report authorization and row level security

[PowerPlop]

Description

Hi,

I was wondering if evidence.dev offers a way to limit data based on user context (Row level security)?
Or do you use a templated SQL to generate pages for every account and limit access to the actual report url?

If we would like to limit access to certain report pages, do we have to use a proxy or other tooling?
I understand authentication is not part of the community version of Evidence.dev but maybe the current stack offers another solution?

Kind regards

What problem would this solve?

No response

How should it work?

No response

[archiewood]

Currently the best model to do RLS style access controls is by managing different deployments for different users.
Since each deployment is simply a static site, this is a relatively lightweight solution.

You can combine multiple deployments with build time variables to filter the data per user, and that way create totally sandboxed data for each user.

Evidence Cloud has features to make the managements of these deployments straightforwards.

[PowerPlop]

So if we would have 5 sales manager representing each a district and they should not be allowed to see each other figures, you would deploy 5 times and manage access through different sub-domains etc.?

[archiewood]

either sub domains or sub routes with separate storage behind them

[PowerPlop]

Thanks for the swift reply!