> ## Documentation Index
> Fetch the complete documentation index at: https://docs.octokraft.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Project Settings

> Configure your Corbulo project

Projects are workspaces that group related repositories and team members. Each project has its own health scores, analysis settings, and team permissions. Configure everything from **Settings** in the left sidebar.

## General Settings

| Setting         | Description                                         |
| --------------- | --------------------------------------------------- |
| **Name**        | Display name for the project                        |
| **Description** | Brief summary of what this project covers           |
| **Slug**        | URL-friendly identifier (used in links and the API) |

## Analysis Settings

Control how Corbulo analyzes the code in this project.

### PR Analysis

Enable or disable automatic analysis of pull requests. When enabled, Corbulo analyzes every new or updated PR in connected repositories and surfaces issues, classification, and merge readiness.

### Architecture Reviews

Enable or disable periodic architecture reviews. These evaluate modularity, coupling, scalability, and pattern consistency across your repositories.

### Analysis Triggers

Configure when analysis runs:

* **Automatic on PR open/update** -- analysis runs whenever a PR is opened or new commits are pushed
* **Manual only** -- analysis runs only when you trigger it from the dashboard

## Repository Management

Add or remove repositories from the project in **Settings > Repositories**.

* Each repository is analyzed independently but contributes to the project-wide health score
* Repositories can belong to any GitHub organization you have connected
* Removing a repository from the project does not affect the repository on GitHub

<Tip>
  Group related services into a single project for cross-repository visibility. For example, a microservices backend and its frontend could share one project.
</Tip>

## Dismissed Rules

Manage global dismiss rules that suppress specific findings across the project. Dismissed rules are excluded from health score calculations.

Configure dismiss rules in **Settings > Dismissed Rules**, or dismiss individual findings inline from the Code Health or PR Analysis views.

<Note>
  Every dismiss rule records who created it and why. Document the reason clearly so the team understands the context later.
</Note>

See the [Code Health](/features/code-health) docs for details on how dismissals work.

## Danger Zone

Irreversible actions that affect the entire project.

### Delete Project

Permanently removes the project and all associated data: analysis history, health scores, team associations, and settings. This cannot be undone.

### Transfer Ownership

Transfer project ownership to another team member. The new owner gets full control, and you become a regular member.

1. Navigate to **Settings > Danger Zone**
2. Click **Transfer Ownership**
3. Select the new owner from your team members
4. Confirm the transfer

<Warning>
  Deleting a project is permanent. If you are unsure, consider removing repositories individually instead.
</Warning>