---
title: Projects
description: A Project is a shared workspace that bundles files, chats, agents, and instructions around a specific piece of work — a customer, a launch, a long-running investigation.
---

A Project is a shared workspace that bundles files, chats, agents, and instructions around a specific piece of work. Where a single chat is a one-off question, a Project is the place a team keeps everything related to a customer, a launch, a long-running investigation — and the agents that work over those materials.

This overview names the pieces and points at the per-piece pages. The concept page goes deeper on when a Project beats a stand-alone chat and how the parts compose.

## What a Project bundles

Each Project carries five things visible from its sidebar: **Files** uploaded once and reused across every chat in the Project, **Threads** (the chats started inside it), **Agents** scoped to the Project, **Instructions** that prepend every agent's instructions when it runs inside the Project, and **Settings** for sharing and lifecycle. Members of a Project see the same view; the Project, not the user, owns the data.

## Pages in this section

**[Project concepts](/platform/projects/concepts)** — the mental model: what a Project owns, when to reach for one, how Project agents shadow org agents.

**[Manage files](/platform/projects/manage-files)** — uploading, replacing, deleting, and the per-Project size limits.

**[Project agents](/platform/projects/project-agents)** — Project-scoped agents versus org agents; the shadow rule; publishing into a Project.

## Where this fits

Projects sit beside Chat in the sidebar. The handover is natural: most users start a question in Chat, realise it is bigger than one chat, and move it into a Project. The next read depends on whether you are building the Project or working in one — [Use projects](/tutorials/member/use-projects) walks a fresh Project end to end; [Project concepts](/platform/projects/concepts) names the model.
