Some of our users are unable to access their own personal folders. It just shows a blank screen.
We’ve looked into access permissions and it doesn’t seem to be the issue. They have access to view and edit their own folders.
When looking into the folder as an admin, we can see the folder, but when sudo-ing as the user it also produces the same blank screen error.
The workaround we’ve created so far is to create a sub-folder within the users folders and copy their looks to that folder instead and this works
Has anyone encountered this before?
2 Likes
Hi @aramostgtg This does not look like a permissions issue because the problem also happens when you sudo as the user and admins can see the folder. Since creating a subfolder works, the most likely cause is that the original personal folder object is in a corrupted or inconsistent state. This can happen if the user was deactivated and reactivated, if ownership was changed in the past, or if there was a backend inconsistency. You can try checking the folder ownership through the API to confirm the correct user ID, listing the folder contents through the API to see if it returns data, or temporarily transferring ownership to an admin and then back to the user. If the issue remains, it is most likely a backend bug and should be reported to Looker Support, as it cannot be resolved through UI permissions alone.