I’m experiencing an issue with sharing my Data Studio (Looker Studio) dashboard. When I open it, I’m able to edit the dashboard and view it with no problems, as can some of my coworkers. Problem is, we share these dashboards with clients (and some coworkers that view the data but don’t need edit access) - unlisted, view only permissions - and they are getting an error that prevents them from seeing anything on it. It reads:
“Authorize Data Studio API
To continue using Data Studio please authorize the app to securely access your account data.”
We’ve found a fix - our client and the coworkers that are getting this error can go into an incognito window on Chrome and view the dashboard just fine there. I also tried making a copy of the dashboard, but it provided the same error to my coworker who had the error on the first version too. Wanted to ask - has anyone here encountered this before?
Appreciate any help here! Just trying to understand the reason this is happening, and trying to get my client to not have to use incognito mode to view what should be a finished product. Thanks!
Have been having this issue for a week or so now. We are a High School and it seems as though since the rebrand, students (marked in Admin Console as under 18) are no longer able to view and DataStudio pages once their oAuth token expires. I discussed with Google Workspace support and they seemed to think there was a bug logged for a similar issue but could not give me any further details.
As soon as I move a student into a staff OU (marking their account as over 18) access is immediately granted again, so I felt as though it was related to some changes with the age restrictions and DataStudio recently, but your experience differes slightly.
I have this problem too since about 6:00 PM on 5/18/26. This affects all our dashboards that use BigQuery or Google Sheets data sources to which access is restricted. I can view if I change to use viewer credentials, but using owner’s credentials is not working at all right now. Help?
Our students get re-directed to families.google.com due to what seems a hard-coded over 18 requirement of DataStudio.
Is everyone in Commercial/Enterprise getting the error 400 listed above when you try to authorise the API? I can’t really troubleshoot any further because we only see it on student accounts currently.
This page mentions the 400 error, has anyone checked this out?
If a user receives an Error 400: invalid_scope message when attempting to authorize the app, then the user’s organization has not or incorrectly authorized the app. To resolve the issue, the user will have to request that their organization authorize the app.
We are experiencing this issue as well; when some partners visit our report, they are directed to login. Partners do not all have google logins, so this bug threatens our ability to share information with partners and we may need to switch sites if the bug cannot be addressed.
About a third of partners have faced this challenge, we have not yet been able to pinpoint why some have the challenge and others do not. It has primarily seemed to occur in chrome, but it has seemed to occur across multiple device types and login statuses.
Updated to note that error persists even after a hard refresh and after manually deleting cached files/images.
Hi! Data Studio eng here. I was not able to repro the issue with Edu users under 18 - If the admin has enabled Data Studio for their users, and has not set any age-based restriction, Data Studio does not block underaged Edu users.
Do you mind DM me one of the account emails that ran into the issue so we can take a closer look on our side?
Hi JingG, I’m not sure where to DM you. My test student account now works (wasn’t working yesterday). Our filtering shows students still getting redirected approx 20 hours ago. I can supply usernames for some who were affected if I can email you?
Any updates on the resolution of this error? We have our reports set to be public and want to make sure users without Google accounts are able to view them. We have reports of users receiving this error and being directed to login.
