we have an ongoing issue with looker studio. As we share our reports and dashboards with our clients, we have to manage the access to the shown data. All our reports and dashboards are access restricted and only usable with Data Viewer rights.
In our Dashboards URLs are shown as clickable links.
Since today there is an ongoing issue with that. URLs cannot be rendered while using viewers credentials, as seen in the screenshot.
We could switch to owner’s credentials but we want to guarantee the maximum of data privacy and so the switch to owner’s credentials is no option for us.
Is there anyone with the same issue?We have a lot of clients with a lot of dashboards and all are affected. Therefore, we would appreciate a quick bug fix.
This is expected behavior, due to a recent change. Links to URLs that use data from the data source no longer work for data sources with viewer’s credentials. We had to make this change to prevent a report creator from gaining access to data when a report viewer clicks a link on a report with viewer’s credentials.
Links to URLs that use data from a data source with viewer’s credentials DO work if the report creator and the viewer are in the same team workspace. In this scenario, both the report creator and the report viewer are part of the same organization. We’re going to add the ability for workspace admins to disable these kinds of links, to provide additional security.
We’ll also add a way for report viewers to opt in to using data, obtained with their credentials, in links — we’ll do this for both the Free and Pro plans. Stay tuned!
This change is really impacting on how viewers access their data through a common report. I hope the option for them to permit such access will be coming soon.
I was unaware that there was a means by which report creators could access viewers private data - could you provide more detail on that please ?
This is expected behavior, due to a recent change.
This is unfortunate, as it causes significant problems for our customers when using the dashboards in this environment. Resolving this issue will require considerable effort. It is regrettable that agencies were not taken into account in this release.
We’ll also add a way for report viewers to opt in to using data, obtained with their credentials, in links
That would be interesting for us. We are very unhappy with the current situation and would appreciate receiving further information about this as soon as possible.
This has also led to significant expenses for us, because dozens of our dashboards can no longer be used by our customers.
Yesterday, three colleagues and I spent the entire day converting the URL type to string and replacing hyperlink functions in hundreds of data sources. Today, we will have to continue.
I find it completely incomprehensible how such a breaking change can be implemented without proactive communication and any consideration of the implications.
I sincerely hope that the opt-in option will be implemented soon. My team and I are already looking forward to converting all data types back to URL.
We’re currently dealing with a broken dashboard infrastructure for which there’s no workaround. Several clients are looking at dashboards filled with cryptic error messages — to them, they simply look broken.
Hi @JenS , any updates on this topic? The fact that our dashboards no longer contain links is a major disadvantage in terms of usability. It would be great if the opt-in option could be implemented as soon as possible so that we can change the data type back.
Could you please at least let us know whether work is (still) being done on the update? As I said, we have dozens of customer dashboards here that rely on this feature. If the opt-in option is not coming, we will have to come up with something else. But I need clarity on this. Therefore, after more than a month, at least a sign of life would be very welcome.
Thank you very much and have a good start to the week.
Exhausted the idea of using Viewer’s Credentials and Service Account Credentials to apply RLS to the reports using the SESSION_USER() function with look up tables to the underlying data that includes URL’s.
This change seems to be directionally aligned to getting us to pay for Looker Studio Pro licenses per User that is logged in to provide them RLS.
One of the work arounds I found is filtering the data once in Looker Studio..
We would use the USER_EMAIL() function to then apply the filter to the data source, once all the data was loaded in to Looker Studio. Unfortunately we are loading several versions of the same data that then applies to the USER_EMAIL() row by row.
Seems a bit silly to load a bunch of repetitive data, just to filter in by USER_EMAIL() once in Looker.
The other was using parameters and hiding in an iframe that does not expose the URL in the browser window. However, a smart user, can figure out how to change the parm and gain access to other orgs/users data by changing the parms.
