> 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/2025.2/instance-administration/analysis-functions/instance-mode/standard-experience.md).

# Standard Experience

The Standard Experience in SonarQube Server 2025.2 encompasses the use of rule types such as bugs, code smells, and vulnerabilities, with a single type and severity level for each rule.

This approach focuses on assigning severity to a rule based on the single software quality (e.g. security, reliability, or maintainability) it has the largest impact on.

## How severity works in Standard Experience mode <a href="#se-severity" id="se-severity"></a>

| **Severity** | Definition                                                                                                                                                                                                                                                                     |
| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Blocker      | An issue that has a significant probability of severe unintended consequences on the application that should be fixed immediately. This includes bugs leading to production crashes and security flaws allowing attackers to extract sensitive data or execute malicious code. |
| Critical     | An issue with a critical impact on the application that should be fixed as soon as possible.                                                                                                                                                                                   |
| Major        | An issue with a major impact on the application.                                                                                                                                                                                                                               |
| Minor        | An issue with a minor impact on the application.                                                                                                                                                                                                                               |
| Info         | There is no expected impact on the application. For informational purposes only.                                                                                                                                                                                               |

## Related pages <a href="#related-pages" id="related-pages"></a>

* [MQR mode](/sonarqube-server/2025.2/instance-administration/analysis-functions/instance-mode/mqr-mode.md)
* [Changing instance modes](/sonarqube-server/2025.2/user-guide/code-metrics/changing-modes.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/2025.2/instance-administration/analysis-functions/instance-mode/standard-experience.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.