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

# Projects

> A project is the container for a domain or set of URLs you want to audit together.

A **project** is a single audit context: one brand, in one market, with the set of URLs you want measured together. It's defined by a project name, a primary domain, and the language and country you're auditing for — those settings shape how ICPs and prompts are generated. All URLs in a project share the same ICPs, prompts, snapshot schedule, and visibility metrics, so everything inside a project is measured against the same audience and the same competitive landscape.

## What a project contains

Each project has its own:

* **URLs** — the pages you want audited
* **ICPs** — Ideal Customer Profiles extracted from your content
* **Prompts** — audit prompts generated from your ICPs and page content
* **Snapshots** — weekly re-runs of the full audit pipeline
* **Recommendations** — prioritized content and technical fixes per URL and prompt

## When to create a new project

You can run as many projects as you have slots for, and each one runs independently — its own URLs, ICPs, prompts, and snapshot schedule. Create a separate project whenever the audit context genuinely differs:

* **A different brand or domain** — each brand gets its own ICPs, competitors, and metrics.
* **A different market** — the same brand audited in another country or language. ICPs and prompts are generated per language and country, so a German audit and an English audit belong in separate projects.
* **A distinct product line or site section** that serves a different audience and would otherwise dilute the ICPs.

Keep a single project when the URLs share the same audience and market. Splitting them up fragments the topic clusters and cross-URL analysis that let your pages reinforce each other.

<Tip>
  Rule of thumb: one brand, one market, one project. Reach for a new project when the *audience* or the *language/country* changes, not just because you have more URLs.
</Tip>

## Team members

A project can be shared with **unlimited team members** — there's no cap on how many people you invite. Invite teammates by email from the project's settings, and they get access to that specific project.

Members hold one of three roles:

* **Owner** — full control of the project, including inviting and removing members and archiving it. Every project keeps at least one owner.
* **Editor** — can run audits and work with the results.
* **Viewer** — read-only access to the audit and its results.

<Info>
  Seats are scoped to a single project. Inviting someone to one project doesn't give them access to your other projects.
</Info>

## Slots

Projects live in **slots**. Each slot is a licensed capacity unit tied to your plan. You can have slots without projects attached (ready to assign), and you can reassign a project from one slot to another.

Every account includes a free **demo slot**, which is a scoped trial version of the full product. Each paid slot you add also unlocks an additional demo slot, so agencies and teams can explore more brands alongside their active client work.

## Archiving a project

Archiving removes a project from your active workspace while preserving its slot.

* **Before ICPs are confirmed** — archiving is immediate. The slot becomes available again right away and you can set up a new project in its place.
* **After ICPs are confirmed** — the project is restorable for **7 days** after archiving. Use that window to bring it back without losing any work.
* **Past the 7-day window** — the project's analysis data is permanently deleted. Paid slots then enter a **cooldown period** before becoming available again; demo slots unlock immediately.

<Tip>
  If you archived a project by mistake, restore it within 7 days. After that the content is purged and the slot enters cooldown.
</Tip>