Model columns can't filter for users with no database access

Get Help
1

Hello,

We've got two user groups in Metabase: one with access to databases and one without.

When I convert a table directly into a Model for users without database access, they can't use the filter column feature. However, I can (with db access).

Below is what it shows on my end (with capability to filter with dropdown)

Screenshot 2024-05-16 at 12.22.22 PM
Screenshot 2024-05-16 at 12.22.22 PM552×716 16.3 KB

I found a workaround: instead of converting a table directly into a model, I write a select all query and turn a question into a model. With this, restricted users can filter the columns. But, the column filter is via a free text field, not a dropdown list of unique values.

With sql query, both me and restricted users can only filter with free text field

Screenshot 2024-05-16 at 12.23.34 PM
Screenshot 2024-05-16 at 12.23.34 PM712×746 25.2 KB

Is there a method for restricted users to filter with a dropdown list?

2

Could you please clarify what you mean by "without access to databases"? How exactly are data, permission and application permissions set up for the "restricted" group?

3

Thanks for the help. We figured out to grant users with access to specific tables so they can use filters.

4

was the model a SQL query or a GUI query?

5

For users with no database access, the GUI version forbids filtering capabilities, while the SQL version only allows for free text filtering.

I want to implement a dropdown list for filtering, which I already have. My role grants full access to the database tables, but our users do not. I'm unable to find a solution that allows users with no- self-service roles to perform dropdown filtering through a GUI model.

Therefore, our current solution is to grant granular access to specific tables in the database for these users.