SonarQube Server Enterprise Edition v2026.3 (123014)
how is SonarQube deployed: Docker
what are you trying to achieve:
Enable project-level permission management for project admins
what have you tried so far to achieve this:
Set the global setting “Enable permission management for project administrators” to enabled. It had been disabled.
Re-applied permission template to project.
Created a new project, with permission template auto-applied.
Project admin logged out of SonarQube and logged back in and was still not able to view project-level permissions.
I am a SonarQube system administrator and am assisting development teams to implement and configure SonarQube analysis for their projects.
I manually gave all permissions (including Administer) to a user (Project Admin) in a specific project. I also created a permission template that included that user with the same permissions.
The Project Admin was then able to see the “Project Settings” menu item in the project, however the “Permissions” item was not included in the menu.
I then realised that the global setting “Enable permission management for project administrators” was disabled.
I enabled the setting.
The following day, the Project Admin tried again but the “Permissions” option was still not visible in the Project Settings menu.
They were able to follow a link I provided to the permissions page. The list was empty with the message: “We couldn’t find any results matching selected criteria.”
I re-applied the permission template that included the Project Admin with all permissions.
The Project Admin created a new project (via Azure DevOps CI pipeline). The new project was created fine. I could see the permissions template had been automatically applied correctly, however the Project Admin could still not see the Permissions item in the menu or any actual project permissions.
I have queried the global setting via the API and the value is “true”, which aligns with the UI.
Hey @Hayley, welcome to the Community! This sounds very similar to an issue that was fixed recently where project admins were receiving a 403 from a GET /api/v2/dop-translation/gitlab-configurations request made by the web app, even when the project was not even bound to Gitlab.
Could you ask your project admin to have a look at their browser’s network tab? Do they see anything similar to what I described when accessing the URL directly? Which requests are failing?
Also: you said you’re running version “v2026.3 (123014)”. I’m assuming you’re on 2026.3.0, because that’s the one to which build number 123014 corresponds to, but could you please confirm this? This is important because, as this is a recently-fixed issue, I want to know if perhaps you’re on an affected version or if there has been a regression.
Hmm okay, it doesn’t seem to be similar to that known (and solved) issue that I mentioned. What you are seeing really looks as if sonar.allowPermissionManagementForProjectAdmins was set to false. Ultimately, SonarQube stores this prop in the DB, and checks it via this query:
select p.prop_key as "key", p.is_empty as empty, p.text_value as textValue, p.clob_value as clobValue, p.entity_uuid as entityUuid, p.user_uuid as userUuid from properties p where p.prop_key='sonar.allowPermissionManagementForProjectAdmins' and p.entity_uuid is null and p.user_uuid is null;
Could you run this query and see what you get? I know you already checked via API but I want to be sure. Note that if no rows are returned, then it means the prop is set to the default value (true in this case).
I apologise for the extended delay in replying. There has been some access issue that are taking longer than expected to resolve. This is still an issue and still on my radar. I will try to get you the requested info ASAP.
Hey @Hayley, no worries! Let’s try a different approach: is this issue happening to all project admins or only to this one particular user? The “Enable permission management for project administrators”/sonar.allowPermissionManagementForProjectAdmins setting is global, so if it was the case that this setting was somehow disabled, then other project admins would suffer from the same issue.
Assuming the issue is not widespread to other project admins: let’s say there’s user X, who is admin of project A, and user Y, who is admin of project B. Could you compare users X and Y permissions, both globally and in their respective projects? Could you also try what happens if you grant user X project admin permission on project B and user Y project admin permission on project A? Will they still get/not get the issue in this cross-project type of fashion?
The issue is not limited to a single user. Before submitting this question to the community board, I checked with another individual who I knew was a project-level admin for multiple SonarQube projects. They were also not able to view project-level permissions.
A couple of weeks ago my SonarQube admin permissions were temporarily removed. At that time I looked at some SonarQube projects for which I have project-level admin permission and I also could not see the Permissions option in the Project Settings menu and could not see project-level permissions.
This has not always been the case. Prior to having system admin permission I was a project-level admin for many projects and definitely could see and update project-level permissions. I am not sure when the issue of project-level permissions first appeared as editing them was not something I was doing regularly.
Hey @Hayley, okay, thanks for confirming. So to summarize: you have set “Enable permission management for project administrators”, but multiple project admins cannot access the project permissions settings. At this point I’m going to flag this for the devs because I’m running out of ideas and I’m starting to think that this sounds like a bug indeed, thanks for the patience!
Do you happen to have more information on how your SonarQube admin permissions were temporarily removed? Was there any script editing permissions or anything of that nature?
The removal of my SQ admin permissions wasn’t related to SQ. I was accidentally removed from the Active Directory group that provides the SQ admin permissions.
How was this user made a project admin for that specific project? Was it directly in the permissions page or through a permissions template? Also, would this be by group or by user?
Are you able to see what the user’s permissions are directly in the project’s permission page? Does the user have the project admin permission there?
As a SonarQube admin, I can still see the project permission’s pages and all of the groups/users permissions.
I manually assigned the Administer permission to the specific user via the project’s permission page user interface. I ticked all permissions for the user even though they would inherit most of the others via an existing active-directory group.
This is the default set of permissions available to users, who belong to the specific AD group:
If you can, can you please share what you can for the following:
For the affected user, what does /api/navigation/component?component= return for configuration.showPermissions? The screenshot here shows the component requests return 200, but the field could help give more details.
For one failure, can you please share a sanitized response body, request ID, and UTC time for each 403, including the /api/projects/search… requests? What do the same scoped requests return as a system admin?
Can a fresh local user, outside of AD/SSO, with direct BROWSE and ADMINISTER permissions on that same project access Permissions? In this post, was this user a local user or AD/SSO?