Getting mixed experiences when people with the same level of access view the same question. There is an Accounting group and that group has Query and Native permission on the DB level as well as curate access on the collection level. Basically all the access I can give them without making them admins. They should be seeing the option to use the Filter, Summarize, and Editor buttons at the top of each question like this:
Instead none of them can use or even see these buttons and they are getting different behavior when they go to the dashboard even tho they’re in the same group. One person can get to the card but don’t have the buttons:
and it says “View Only” but I have no idea where that’s coming from because they have greater than viewing access on everything. The kicker here is they were able to see and use these buttons before but then they just disappeared and nothing was changed on the permission level.
I had them clear their cache and cookies, try in an incognito window, and even try and add header=true&action_buttons=true at the end of the question url.
Its in the Metabase UI. All good questions. Sorry this is my first post for help so didn’t know what info would be helpful to include.
Fwiw the only thing I could do to get it to work was to make the other users admins. According to the docs they should be able to filter with less access but it’s nice to have the admin route as a fallback.
Also working on updating to the most recent version of Metabase
Hm, the screenshots you were showing look more like embedded questions, especially the part about changing the URL parameters. The “View-only” badge only appears on embedded dashboards.
I tried to reproduce your problem but wasn’t able to. At least on 0.56, opening someone else’s question allows you to save it to a new question, and the first time you open a question, it puts up a popup telling you to do just that.
We’re all very new to Metabase so I might be confused on what our team set up. If this was an embedded question how would I go about fixing it? I just read something from the docs about the URL params. FWIW it didn’t do anything no matter what I changed them to
I think you need to talk to your Metabase admin team and explain your issues and work with them to set things up to work the way you need them to.
From your description, it’s likely that your Accounting group is accessing Metabase through an embedded dashboard that’s in an iframe on another webpage. On the OSS version of Metabase these static embedded dashboards are read-only. They won’t get edit buttons or the ability to save anything, but they will have access to whatever filters are in the dashboard, unless they’ve been locked through parameters in the authentication token.
Meanwhile, you are logging into the Metabase UI where you have all the read/write options.
