I hope you’re all doing well. I’m reaching out to seek advice on an issue we’re facing with our Looker folder structure and access rights management.
We currently organize user groups and folders in ‘Shared folders’ by team/squad and have an open Looker instance. This approach worked well when we were a smaller company, but as we’ve grown and have more cross-team projects, this structure is becoming less effective. We’re encountering problems with content duplication, reduced usage of shared folders, and difficulties navigating to company-wide dashboards.
To address this, I’m considering maintaining the team/squad-based folder structure but adding cross-team and company-wide folders accessible to everyone for storing project-specific data assets that should be available to a wider audience. I’m curious to know how other companies have tackled similar challenges.
How have you structured your Looker folders to improve navigation and manage access rights effectively? Any insights or experiences you can share would be greatly appreciated.
Hey @sharifahSY , thanks for your reply.
While we know the theoretical aspects of user management, we still struggle with establishing the most effective folder structure. We’re specifically looking for insights from real use-cases rather than the theory provided in Looker’s documentation.
I have implemented a Open System with Restrictions for members of my company that will have Viewer roles for access to Looker. I used the suggestion by @evelyn_s to remove the “All Users” access to the individuals in order to minimize who sees what under the People Shared Folder. A typical user now has this configuration:
Since the members will not be creating or sharing content with others, I would like to remove the People shared folder all together from their Looker left-hand panel.
Is there an attribute or some other approach that would accomplish this in Looker?
