> For the complete documentation index, see [llms.txt](https://know.rendernetwork.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://know.rendernetwork.com/docs/web-app/projects.md).

# Organise work in projects

Create projects, organise existing scenes, and remove scenes from a project.

Use projects to keep related scenes and their jobs together. Think of it as a folder for your scenes.

## Create a project

1. Open **Projects** in the sidebar and click **Create Project** at the top of the page.
2. Enter a name in **Project Name**.
3. Click **Create Project**.

You can also open this window from the **Create Project** card in the project list or the plus button beside **Projects** in the sidebar.

To open a project, double-click it in the project list or expand **Projects** in the sidebar and click its name.

## Rename a project

1. Open the project. If its details panel is hidden, click the project name at the top of the page.
2. Click the pencil beside the name in the details panel.
3. Enter the name, then click the check button or press Enter. Press Escape or click the cross button to cancel.

## Add existing scenes

{% tabs %}
{% tab title="Choose a project" %}

1. Open **All Scenes** and select one or more scenes.
2. Click **Add to project** in the toolbar at the bottom of the list, or right-click the selection and choose **Add to project**. For a single scene in table view, you can also use **Add to project** in its row's actions.
3. In the **Add to Project** window, choose a project from **Select Project...**.
4. Click **Add to Project**.

You can also open this window from the **Add to project** icon in an open scene's details panel. Click the scene name at the top of the page if the panel is hidden. Scene entries in **Activity** in the right-hand panel also offer this action when available.
{% endtab %}

{% tab title="Drag onto the sidebar" %}

1. Expand **Projects** in the sidebar. If **Done Editing** is shown, click it first.
2. In **All Scenes** or an open project's scene list, select the scenes you want to add.
3. Drag one of the selected scenes onto the destination project's name in the sidebar.

The scenes are added directly, without opening the project picker.
{% endtab %}
{% endtabs %}

{% hint style="info" %}
Adding a scene includes its available [versions](/docs/web-app/scenes-and-versions.md) and their existing jobs in the project.
{% endhint %}

For files still on your computer, see [Upload Scenes](/docs/web-app/upload-scenes.md).

## Remove scenes from a project

1. Open the project and select the scenes you want to remove.
2. Click **Remove from project** in the toolbar at the bottom of the list, or right-click the selection and choose **Remove from project**. In table view, you can also use the action in a scene's row.

The scenes disappear from this project but remain available in **All Scenes**.


---

# 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://know.rendernetwork.com/docs/web-app/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.