> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-server/instance-administration/system-functions/security.md).

# Security features

SonarQube Server 2026.5 comes with a number of global security features.

SonarQube Server comes with a number of global security features:

* On-board authentication and authorization mechanisms.
* The ability to force users to authenticate before they can see any part of a SonarQube Server instance.
* The ability to delegate to authentication.
* Enforce an Azure OpenAI Service endpoint URL domain when [Enable AI CodeFix](/sonarqube-server/instance-administration/ai-features/enable-ai-codefix.md#enabling-ai-generated-fix-suggestions).

Additionally, it’s possible to configure at a group or user level who can:

* See that a project even exists.
* Access a project’s source code.
* Administer a project (set exclusion patterns, tune plugin configuration for that project, etc.).
* Administer Quality Profiles, Quality Gates, and the SonarQube Server instance itself.

Another aspect of security is the encryption of settings such as passwords. SonarQube Server provides a built-in mechanism to encrypt settings.

See:

* [User accounts](/sonarqube-server/instance-administration/security/user-accounts.md)
* [Managing groups](/sonarqube-server/instance-administration/user-management/user-groups.md)
* [Managing permissions](/sonarqube-server/instance-administration/user-management/user-permissions.md)
* [Setting project permissions](/sonarqube-server/project-administration/setting-project-permissions.md)
* [Sensitive settings](/sonarqube-server/instance-administration/security/encrypting-settings.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sonarsource.com/sonarqube-server/instance-administration/system-functions/security.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.