Hi Team,
We are using SonarQube 2026.1.0 and have identified behavior that may indicate a permission issue.
Users with only default “sonar-users” group access (Browse permissions) are able to create portfolios successfully, even though they lack administrative rights. However, they are then unable to configure the created portfolios.
This seems like inconsistent permission enforcement.
Can you confirm:
Thanks.
Hey @rahul.phatkare, the permission that controls portfolio creation is neither Browse nor Admin: it’s “Create Portfolios”. Could you check if your sonar-users group has this permission (Administration > Security > Global Permissions)? If not, then perhaps users are getting them through another group. You can check the groups a user belongs to in Administration > Security > Users, and then check the group’s permissions. And finally you should also check if they’re getting this permission assigned individually, instead of via groups.
Regarding your second issue (portfolio creators don’t have permission to configure it), this is likely tied to your permission templates. In case you’re unfamiliar, permission templates are the permissions that are applied as default to newly created projects/portfolios (you can read more here). Go to Administration > Security > Permission Templates, and check if your templates are granting Admin permission to the Creators (special group that applies to the project/portfolio creator).