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

# Projects Overview

> A shared workspace container that groups related chats, pages, flows, tables, and files under one space — with its own AI instructions and access model.

## What is a Project?

A **Project** is a lightweight container that groups the work that belongs together — the chats, pages, flows, tables, and uploaded files for a single initiative — into one shared space. Each project carries its own name, description, and AI **instructions** that apply to the chats and flows scoped to it, plus a per-project **access model** so you can keep sensitive work limited to specific people.

<CardGroup cols={2}>
  <Card title="Group your work" icon="folder">
    Attach pages, flows, tables, and chats to a project so everything for one initiative lives in one place.
  </Card>

  <Card title="Project instructions" icon="wand-magic-sparkles">
    Give the AI standing context for everything scoped to the project — tone, goals, domain facts.
  </Card>

  <Card title="Project files" icon="paperclip">
    Upload reference files (up to 50 MB each) that live with the project and are available to its members.
  </Card>

  <Card title="Access control" icon="lock">
    Share with everyone, keep it creator-only, or grant specific members view/edit access.
  </Card>
</CardGroup>

***

## How artifacts join a project

Projects don't nest other resources under their own routes. Instead, a page, flow, table, or chat **belongs to a project by carrying a `project_id`** — set through that artifact's own API, and queried back with `?project_id=`.

* To **add** a page/flow/table/chat to a project, set its `project_id` via the corresponding Pages / Flows / CRM API.
* To **list** a project's contents, query each artifact API with `?project_id=<id>`.
* The one artifact a project stores directly is **Project Files** — binary uploads managed through the endpoints below.

When a project is deleted, it is **soft-deleted** and its contained pages, tables, and chats are detached (`project_id` cleared) — the artifacts themselves survive and remain findable in the global overviews.

***

## Project Files

Project Files are binary uploads (documents, images, datasets) attached directly to a project and stored in a private bucket. They support full CRUD via the API:

| Action | Endpoint |
| - | - |
| List files | `GET /api/projects/{id}/files` |
| Upload a file | `POST /api/projects/{id}/files` |
| Delete a file | `DELETE /api/projects/{id}/files/{fileId}` |

Listing returns a short-lived (1-hour) signed download URL per file — re-fetch the list to re-sign rather than persisting URLs. Uploads are capped at 50 MB per file and require edit access to the project.

<Note>
  **Project Files are not Workspace Files.** Project Files live with a specific project; Workspace Files are a separate, workspace-level store. They are different features with different endpoints.
</Note>

***

## Access model

Every project has an access mode:

* **Everyone** — all workspace members can view/edit.
* **Creator only** — only the project owner can see it.
* **Specific users** — explicitly shared members, each with a `view` or `edit` role.

Members who lack access see a request-access screen rather than the project. Managing a project's access mode and shared members is an **in-app, owner/admin-only** operation and is not exposed as a public API.

***

## API reference

<CardGroup cols={2}>
  <Card title="Projects" icon="folder" href="/api-reference/projects/list-projects">
    Create, read, update, and delete projects.
  </Card>

  <Card title="Project files" icon="paperclip" href="/api-reference/project-files/list-project-files">
    Upload, list, and delete files attached to a project.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.