UI Bugs in Looker Studio Pro regarding ability to edit datasources

Hi!

We’re using Looker Studio Pro for data source and dashboard management for our company dashboards.

Before moving to Looker Studio Pro, we used (and still practice it) to share edit access to reusable datasources to colleague’s email addresses as well as aliases.

Example on the screenshot below:

(1) - the the data source doesn’t have clickable “edit” button

(2) - there used to be a visible icon to open the data source in a new window, now it is still present but it is not rendered probably - those who didn’t know it existed, wouldn’t possibly find it :smiling_face_with_tear:

The only way for me to go to the editing menu of the dataset is to navigate to the “invisible” button and click on it.

For the problem (1), I found that it seems to occur when the data source is not shared “natively” with anyone, but when people have access to it via Team Workspace in Looker Studio Pro.

Below are two tabs of the same data source (1):

In the data sources that are “editable”, there typically is at least some level of access in the tab “Data source” in the “Share with people and groups” menu.

I would be very grateful if someone looked into this and provided the fix, thanks!

Hey,

Hope you’re keeping well.

This behavior is related to how Looker Studio Pro handles permissions when data sources are shared via a Team Workspace rather than directly to individual accounts or groups. In Team Workspace, members can view and use the data source in reports, but the UI won’t show the Edit button unless they have explicit edit rights on the data source itself. To restore the button, open the data source in Resource > Manage added data sources from a report, then use Share > Share with people and groups to grant Can edit access directly to the user or group alongside the workspace membership.

If the icon rendering issue persists, try clearing cache or testing in an incognito window to rule out browser-side glitches, and report it via Looker Studio Help > Send feedback so the UI bug can be tracked by the product team.

Thanks and regards,
Taz