> 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.3/instance-administration/analysis-functions/analysis-scope/introduction.md).

# Introduction

The project team sets the initial analysis scope of their project and may adjust it by using exclusion features (for more information, see [Setting project's analysis scope](/sonarqube-server/2025.3/project-administration/setting-analysis-scope.md)). As a system administrator, you can define an analysis scope adjustment at the global level in the UI. These settings apply by default to all projects and can be overridden at the project level.

To adjust the analysis scope at the global level, you can:

* Exclude specific files from:
  * The duplication check
  * The code coverage analysis
* Exclude files based on path-matching patterns.

In very few situations, you may have to use the advanced exclusion features.

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

* [Excluding from coverage or duplication](/sonarqube-server/2025.3/instance-administration/analysis-functions/analysis-scope/exclude-from-coverage-duplication.md)
* [Excluding files based on file paths](/sonarqube-server/2025.3/instance-administration/analysis-functions/analysis-scope/excluding-files-based-on-file-paths.md)
* [Using advanced exclusion features](/sonarqube-server/2025.3/instance-administration/analysis-functions/analysis-scope/advanced-exclusion-features.md)
* [Setting project's analysis scope](/sonarqube-server/2025.3/project-administration/setting-analysis-scope.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sonarsource.com/sonarqube-server/2025.3/instance-administration/analysis-functions/analysis-scope/introduction.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.