> For the complete documentation index, see [llms.txt](https://docs.zerve.ai/zerve-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zerve.ai/zerve-docs/notebooks/projects-and-folders.md).

# Projects and folders

Organize your work into projects and folders, and find work shared with you.

Your work in the Workspace lives in **projects**. Each project is a notebook, with its blocks, files, environment and results.

Select **Projects** in the Workspace sidebar to see them:

| View               | What it shows                                                      |
| ------------------ | ------------------------------------------------------------------ |
| **Home**           | Your starting point, with the agent composer for starting new work |
| **My projects**    | Projects and folders you've created                                |
| **Starred**        | Projects you've starred, for quick access                          |
| **Shared with me** | Projects and folders other people have shared with you             |
| **Folders**        | Your folders                                                       |

## Starting a project

Start a project from the Workspace **Home** page, either by describing what you want to the agent, or by creating an empty project. When you describe your work to the agent, Zerve opens it as a notebook or a thread, depending on what you asked. See [Threads](/zerve-docs/agents-in-the-workspace/threads.md).

## Folders

Folders group related projects, such as everything for one strategy or one client. Create a folder from **Projects**, then move projects into it.

Folders also control access. Sharing a folder, or setting it to **Team** privacy, gives access to the projects directly inside it. See [Sharing and privacy](/zerve-docs/administration/sharing-and-privacy.md#folders).

## Cloning projects

If your organization allows it, you can copy an organization's project into your own personal organization. Admins control this in [Organization settings](/zerve-docs/administration/organization-settings.md).

## Downloading a project

Download a project as a Jupyter notebook (`.ipynb`) file with **Ctrl+D** (Windows) or **⌘+D** (Mac).


---

# 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://docs.zerve.ai/zerve-docs/notebooks/projects-and-folders.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.