SonarQube access requirements
Access to SonarQube under SHIP-HATS is controlled through a two-layer model:
- SonarQube subscription and LOC capacity – Determines whether your agency can analyse code using SonarQube.
- Application-level (Project-level) permissions – Determines which users can view projects, run scans, and manage analysis results.
Unlike Atlassian tools such as Jira and Confluence, SonarQube does not require user licences. Instead, usage is measured based on the Lines of Code (LOC) analysed.
Subscription model
SonarQube Enterprise Edition usage is measured based on the number of LOC blocks subscribed.
| Edition | Subscription model |
|---|---|
| SonarQube Community Edition | Shared instance provided by SHIP-HATS |
| SonarQube Enterprise Edition | Billed per block of 400,000 lines of code (LOC) |
Subscription Admins should ensure their subscription includes sufficient LOC capacity for the applications being analysed.
For details on LOC limits, usage alerts, and billing behaviour when limits are exceeded, see
SonarQube Enterprise Edition usage and billing policy.
Access scenarios
| SonarQube subscription available | Project permission granted | Result |
|---|---|---|
| ❌ No | ❌ No | No access to SonarQube |
| ✅ Yes | ❌ No | Can log in to SonarQube but cannot access specific projects |
| ❌ No | ✅ Yes | No access (subscription required) |
| ✅ Yes | ✅ Yes | Can access the application (project) and run code analysis |
Important notes
- Users must log in to SonarQube at least once before they can be assigned project permissions.
- Assigning project permissions does not automatically grant access to analyse code if the subscription does not include sufficient LOC capacity.
- LOC usage increases as applications (projects) and codebases are analysed.
- Subscription Admins should monitor LOC usage to avoid exceeding subscription limits.
