I've found previous topics that are similar to this issue, but not quite the same.
On questions, but not on dashboards, dropdown filters for variables will allow for multi-selection of options, selected from a list. This can be restricted, based on permissions of the joined tables that the variable refers to.
For example, if I have a table of schools, and I refer to it in a question via a variable, a dropdown filter can be added which allows for selection of any number of those schools, from a list. If I prevent a user's access to the schools table, they can still use the filter, and view the question, but cannot select options from a list.
The exception comes in when a referred to table is linked to the User table. In that instance, no matter the permissions, for any non admin user, the dropdown list will not appear. I can give identical visibility and permissions to a user who is not an admin, but under no circumstances will that drop down list appear in the filter.
This results in a difference of this:
To this:
The difference in what is observed between an admin user, and a full permissions "Normal" user is the perplexing part. If anyone has observed this, or has any insights, please let me know.
We’ve encountered a similar issue in our reporting boards regarding data access via filters for users with certain permissions. Our system collects user data from the app, and we’ve noticed limitations in how it’s processed based on permission levels.
We reached out to Metabase about this some time ago, but their response was quite delayed, and unfortunately, the issue remains unresolved. From what we can tell, it seems like the paid version of their platform likely includes a solution, whereas the open-source version appears to have restrictions. Certain areas of the system seem to require either paid assistance or an upgrade to the paid version to access the necessary functionality.
Let us know if you’ve found a workaround or if you have any insights.
I do think this must be a limitation (or flaw in) the system, as this behaviour only appears in the Metabase question, but then if that same question is featured on a dashboard, the filters work perfectly.
I do wonder if additional permissions options from the paid version might solve this, but if the paid version didn't solve your issues it will likely be the same for us.
you haven't provided the version you're running, and the reproduction steps for making this happen, it's really difficult to give any advice on this topic without this. Also it would be nice to include the api responses
Hi "Josh" (or Hemant), first of all, it would be really nice if you wouldn't use 2 different names (IndyBond and JoshCallenway) to answer over the same question in the forum, since that would lead me to imply that you're trying to generate engagement over specific topics or threads and I will have to flag every single comment of yours as spam.
Also, please answer these questions with a direct proposal to users if you're willing to help. A good response would be:
please give us the version that you're running
the logs when you click on the filters
the api response of the browser when you click on these filters
a clear reproduction of the same issue using the sample dataset
thank you
EDIT: and please don't lie about our response being "quite delayed", I see you created a ticket on our system in Feb 26, 6:54:43 AM and we answered at Feb 26, 7:02:09 AM (8 minutes after).
Not sure what's going on with this thread at this point, but I do appreciate the help, and will plough on...
I actually managed to resolve this (while replying)! Running through the full details again I realised that the filter was referring to a simple model nested in a sub-directory with different access privileges, I'd forgotten that it had ever been restricted, or even that the model existed.
Tragic to admit how long this took me to work out... I appreciate the help, just being prompted on things is very helpful and thinking through the process rubber duck style is actually very useful. So thanks.
