> For the complete documentation index, see [llms.txt](https://help.chatlyai.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.chatlyai.app/products-and-features/projects.md).

# Projects

Keep related chats and files together, with a goal.

A **project** keeps related chats and files together, with a goal the assistant can see. Use one for each piece of work, like a product launch or a client, so everything for it stays in one place.

## Create a project

1. In the left sidebar, click **+** next to **Projects** (or **New Project** if you don't have one yet).
2. Under **What are you working on**, enter a project name.
3. Under **What are you trying to achieve**, describe the goals for the project.
4. Under **Visibility**, choose your workspace (everyone in the workspace can view and contribute) or **Private** (only you can view and contribute).
5. Click **Create project**.

![The Create project window with name, goals and visibility](https://3503370835-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOHDPAn3RzU7mRQrMH1UK%2Fuploads%2FK7M3nIeNXnxH5cBxaN2x%2Fch-project-new.webp?alt=media)

## Work in a project

Open a project from **Projects** in the left sidebar. The project page shows its name and goals, a chat box, and three tabs:

* **Chats**: every chat you start in the project.
* **Assets**: the files the project uses and creates.
* **Activity**: what has happened in the project.

Type in the chat box on the project page (3) to start a new chat inside the project. You can also add an existing chat to a project from its menu in **Recents** or **My Chats** (**Add to project**).

![A project page with Settings, the Chats, Assets and Activity tabs and the chat box](https://3503370835-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOHDPAn3RzU7mRQrMH1UK%2Fuploads%2Fhmwjn6ujmmOCPY8FUSw7%2Fch-project-page.webp?alt=media)

## Invite people to a project

Click **Settings** on the project page (1), then **Add member** to invite people to work on it with you. The panel also shows who created the project.

![Project settings with Members and Add member](https://3503370835-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOHDPAn3RzU7mRQrMH1UK%2Fuploads%2FNlJJn0nZecAslNQz7mMp%2Fch-project-settings.webp?alt=media)

## Edit or delete a project

Click **⋯** next to the project name and choose **Edit details** to change its name, goals or visibility, or **Delete project** to remove it.

![The project menu with Edit details and Delete project](https://3503370835-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOHDPAn3RzU7mRQrMH1UK%2Fuploads%2FxJ0TO1cPMgPPn9xVchhw%2Fch-project-menu.webp?alt=media)

Private projects show a lock next to their name.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.chatlyai.app/products-and-features/projects.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
