> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.cloudraker.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.cloudraker.com/_mcp/server.

# Projects overview

A **project** is where the actual work happens. It keeps everything for one piece of work in one place: the files you upload, the playbooks the project can run, the runs those playbooks produce, the records they collect, and the people who can see it. You create one project per piece of work — an onboarding, a claim, a contract review.

You open a project from the **Projects** group in the sidebar. Recent projects appear there directly; click **Show more...** to reach the full list.

## A project at a glance

Every project has:

* A **name** — what the work is, like "Acme Corp" or "Pre-screening review".
* An **icon** — picked from a curated set.
* A **project number** like `PRJ-1` or `IMM-42` — the letters are a prefix and the number increments automatically. It shows in the header and under the **Number** column in lists.
* A **status** — **Open** or **Closed**.
* An optional **description** — notes for anyone working on the project.
* An **access list** — the roles and people who can see and edit it.

A project can be built from scratch or created from a project template, which copies in a ready-made setup. See [Create a project](/projects/create-a-project).

## The project header

The header sits at the top of every project. It shows the project **icon**, a breadcrumb (**Projects** > the project **Number**), the project **name**, and a **status badge** — green for **Open**, grey for **Closed**.

On the right is a **"..."** menu. If you can close projects, it holds **Close project** (when the project is Open) or **Reopen project** (when it's Closed).

If a closed project still has runs in flight, a banner appears: "This project is closed, but N run(s) is/are still active." Reopen the project to act on them, or let them finish on their own. Closing and reopening lives in [Create a project](/projects/create-a-project).

## The tabs

Below the header is a row of tabs. Each one is its own area. **Files** is where the project opens by default.

Here is what each tab is for and where to learn more.

The project's reusable file pool — everything uploaded, produced by tasks, or generated by runs.

A snapshot of the project: what's running now, your tasks, recent project actions, and finished work.

The kinds of data this project tracks — like Claims or Invoices — and the details each one captures.

The processes this project can run, each with a **Run** button to start one.

The runs happening inside this project, with their status and progress.

Ad hoc actions run over this project's files or data, with the results to review.

The project's name, icon, description, and who has access.

The **Overview** tab gives a live summary but isn't an area of its own — its cards (**Happening now**, **My tasks**, **Project actions**, **History**) are shortcuts into the tabs above. Your personal task list across every project lives in [My work](/work/my-work).

## Where to go next

Start a project from scratch or a template, set access, and manage Open/Closed.

Start a run and work through its tasks in the run workspace.

Upload, organize, find, and reuse the project's files.

Work with the records a project has collected.

Build reusable starting points so teams spin up projects the same way every time.

Understand the shape of the data a project tracks.