# Project settings

## Project and application PDF reports <a href="#project-pdf-reports" id="project-pdf-reports"></a>

As a project or application administrator, you can change the PDF report subscription frequency of the project or application:

* **Project-level**: To change the frequency setting for a specific project, navigate to the project’s home page then **Project Settings** > **General Settings** > **Governance**. Under **Project and Application PDF Reports**, select an option from the **PDF Reports Frequency** drop-down menu.
* **Application-level**: To change the frequency setting for a specific application, navigate to the application’s home page then **Application Settings** > **Application Report Settings**, and select an option from the **Application Reports Frequency** drop-down menu.

You have the following options for subscription frequency:

* **Daily**
* **Weekly**
* **Monthly (default)**

{% hint style="info" %}
Users can only download or subscribe to a PDF report for a permanent branch. To set a branch as permanent, go to **Project Settings** > **Branches and Pull Requests** and make sure that the **Keep when inactive** toggle is on for that branch.
{% endhint %}

## Tags <a href="#tags" id="tags"></a>

Project tags allow you to categorize and group projects for easier selection on the **Projects** page. Project tags can be administered from the project home page. Administrators will see a dropdown menu indicator next to the project’s list of current tags (or next to the **No tags** indicator). If the tag you want isn’t visible in the dropdown, use the built-in search input to find what you’re looking for, or create it on the fly.

## Administration items <a href="#administration-items" id="administration-items"></a>

Project administration is accessible through the **Project Settings** menu of each project.

Only project administrators can access project’s settings (see [Security features](/sonarqube-server/10.7/instance-administration/system-functions/security.md)).

### Adding a project <a href="#adding-a-project" id="adding-a-project"></a>

A project is automatically added at its first analysis. You can also create and import projects before the first analysis and automate the creation and import of projects using the Web API. See [Creating and importing projects](/sonarqube-server/10.7/project-administration/creating-and-importing-projects.md) for more information.

### Analysis report processing <a href="#analysis-report-processing" id="analysis-report-processing"></a>

A project-level background tasks page is available at **Project Settings > Background Tasks** to allow project administrators to check their projects’ processing. It offers analysis report details and logs.

### Deleting a project <a href="#deleting-a-project" id="deleting-a-project"></a>

**Deleting a single project**

You can delete a project through **Project Settings > Deletion**.

**Deleting multiple projects**

You can also delete multiple projects simultaneously from the global **Project Settings > Projects > Management**.

### Updating the project key <a href="#updating-the-project-key" id="updating-the-project-key"></a>

The project key can be updated (without losing the history on the project) at **Project Settings > Update Key**.

The new key must contain at least one non-digit character. Allowed characters are: `a` through `z`, `A` through `Z`, `-` (dash), `_` (underscore), `.` (dot), `:` (colon) and the digits `0` through `9`. This value is case-sensitive.

### Default issue assignee <a href="#default-issue-assignee" id="default-issue-assignee"></a>

When new issues are created during analysis, they are assigned to the last committer where the issue was raised. When it is not possible to identify the last committer, issues can be assigned to a default assignee, at **Administration > General Settings > Issues.**

### Setting quality gate and quality profiles <a href="#setting-quality-gate-and-quality-profiles" id="setting-quality-gate-and-quality-profiles"></a>

Project administrators can select which of the following to use on their project:

* Quality profiles (go to **Project Settings > Quality Profiles**)
* Quality gate (go to **Project Settings > Quality Gate**)

### Setting exclusions <a href="#setting-exclusions" id="setting-exclusions"></a>

See the [Analysis scope](/sonarqube-server/10.7/project-administration/analysis-scope.md) page.

### Customizing links <a href="#customizing-links" id="customizing-links"></a>

On top of standard links which may only be set as [Analysis parameters](/sonarqube-server/10.7/analyzing-source-code/analysis-parameters.md), additional custom links can be added through the web interface (under **Project Settings > Links**). Those links will then be displayed in the **Project Information** page.

### Marking a project as containing AI-generated code <a href="#marking-a-project-as-containing-ai-generated-code" id="marking-a-project-as-containing-ai-generated-code"></a>

You can mark a project to indicate that it contains AI-generated code. To do this go to **Project settings** > **AI-generated code** and activate the **Contains AI-generated code** setting.

When you activate this setting:

* the [Quality gates](/sonarqube-server/10.7/instance-administration/analysis-functions/quality-gates.md) is enforced on the project:
  * If the project already uses the Sonar way quality gate, activating the setting will lock the project’s quality gate.
  * If the project does not use the Sonar way quality gate, activating this setting will change the project’s quality gate to Sonar way and lock it.

    Locking the Sonar way quality gate ensures that the AI-generated code is clean by enforcing high quality standards.
* The project will have the AI code assurance label:
  * an **AI Code** label is displayed next to the project in the UI
  * you can use the [Using a project badge](/sonarqube-server/10.7/user-guide/project-badge.md) to promote your project’s health


---

# Agent Instructions: 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:

```
GET https://docs.sonarsource.com/sonarqube-server/10.7/project-administration/project-settings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.