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

# Projects

> Create and manage the projects Beeze uses to organize brands, sites, and reporting contexts

Projects are how Beeze separates one brand, site, or business unit from another.

Projects control the reporting context across AI Search, link building, and analytics — most data views are scoped to the active project.

## Why projects matter

A clean project structure helps you:

* keep reporting separated by brand or site
* compare performance without mixing datasets
* organize teams working across several properties

## What a project includes

| Field         | Why it matters                                        |
| ------------- | ----------------------------------------------------- |
| Name          | The label your team sees throughout the product       |
| Slug          | The stable identifier used in app context and linking |
| Domain        | The site or brand the project represents              |
| Color         | A visual cue in project-related UI                    |
| Active status | Whether the project is available in current workflows |

## What you can do

* create a project
* edit a project
* deactivate or reactivate a project
* delete a project

## Plan limits

Beeze shows how many projects your plan includes so you can see whether you have room to add another one.

<Note>
  This is especially relevant for agencies and multi-brand teams. See [Billing](/settings/billing)
  for plan-level project limits.
</Note>