SonarQube roles and permissions
SonarQube permissions determine what users can view and manage within a SonarQube application (project).
Permissions are assigned to users or user groups and control access to project settings, issue management, and code analysis results.
In SHIP-HATS, SonarQube permissions help ensure that only authorised users can administer projects, analyse code, or review security findings.
Permission types
The following table describes the permissions available in SonarQube.
| Permission | Description |
|---|---|
| Administer | Access project settings and perform administration tasks. |
| Administer issues | Change the type and severity of issues, resolve issues as fixed, won’t fix, or false positive. Users also need the Browse permission. |
| Administer security hotspots | Review and resolve security hotspots. Users can mark them as fixed or safe, or reset them for review. Requires the Browse permission. |
| Browse | Access a project and view its measures and issues. Users can confirm issues, change the assignee, comment on issues, and update tags. |
| Execute analysis | Allows users to retrieve settings required to run code analysis and push analysis results to the SonarQube server. |
| See source code | View the project’s source code. Requires the Browse permission. |
How permissions are used
SonarQube permissions support different responsibilities within development teams:
- Project administrators manage project settings and user access.
- Developers run code analysis and review issues detected in their code.
- Security reviewers review and resolve security hotspots and vulnerabilities.
Permissions can be assigned to individual users or user groups, depending on how your organisation manages access.
