You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a great tool and takes away the burden of creating tons of reports for individual clients but just letting them make their own reports. However, there is also my point. How am I supposed to manage the fact that one client should only see his data? Is there some hook where I could change the query?
Another way would be to provide the queries and disallow the edit, but then there one would need a way to inject the current user as immutable variable. If there is currently no way to inject the user as fixed variable and since it is open source, where would you add (allow) such a feature to be added?
The text was updated successfully, but these errors were encountered:
The app isn't really designed for multi-tenancy and there isn't a simple way to do this. For example, you would have to filter querylogs, connections, etc.
If you were only trying to display the results to particular users, that is (in theory) supported via the EXPLORER_GET_USER_QUERY_VIEWS settings, which you can set to a dictionary like:
It's a bit clunky in that you would likely have to modify the code each time you needed a permission change. You can see more how it is implemented here:
This is a great tool and takes away the burden of creating tons of reports for individual clients but just letting them make their own reports. However, there is also my point. How am I supposed to manage the fact that one client should only see his data? Is there some hook where I could change the query?
Another way would be to provide the queries and disallow the edit, but then there one would need a way to inject the current user as immutable variable. If there is currently no way to inject the user as fixed variable and since it is open source, where would you add (allow) such a feature to be added?
The text was updated successfully, but these errors were encountered: