Hi!
SEC over here in my organization have issues with sonar-users being able to browse all projects, that is why users in general don’t have that permission. Our portfolios however are public and we have a couple of users that help build those portfolios by manually adding projects to them. These users have Administer permissions to the portfolio but they don’t have Browse permissions to all projects, and thus not all projects show up when they try to search for them to add in Edit definition.
My idea is to create a new group, something like “Portfolio_admins” that I can give the Browse Permission to all projects. At least then the access to all projects is limited in scope. There’s another question there about adding permissions to multiple projects en masse, but I opened a separate thread for that - so that’s probably gonna be resolved shortly: Give a new group permission to existing projects - SonarQube - Sonar Community (sonarsource.com)