> For the complete documentation index, see [llms.txt](https://docs.guideflow.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guideflow.com/help/dashboard/create-edit-and-manage-subfolders.md).

# Create, edit, and manage subfolders

Create, edit, and manage subfolders to further organize your workspace. (e.g. create subfolders for different projects within a department)

#### **Create and edit your subfolders**

{% @guideflow/guideflow-embed requestedUrl="<https://app.guideflow.com/player/zpeq3gwa3p>" %}

* To add a new section, click the "+" button above your folders and select "Add section".
* To add a subfolder within a section, click the "+" button within the section.
* Edit your subfolder's name.
* If you want, edit your new subfolder's emoji.
* To rename or delete a subfolder, click on the "..." button next to the subfolder and select "Rename" or "Delete".

#### **Organize your subfolders**

Organize subfolders to maintain a clear structure in your workspace.&#x20;

To move a folder into a section:

* Select the folder you want to move.
* Drag & drop this folder into the desired section.
* The folder will now be a subfolder within that section.

{% hint style="info" %}
Remember, a folder can exist either within a section (as a subfolder) or on its own outside of any section.
{% endhint %}


---

# 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.guideflow.com/help/dashboard/create-edit-and-manage-subfolders.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.