> For the complete documentation index, see [llms.txt](https://help.boomerang3.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.boomerang3.com/boomerang-2-system-administrator-manual/tree_view/add_a_new_folder.md).

# Add a new folder

You can create folders in a tree view and move the nodes and sensors between them the way you want. For bigger systems it helps you to keep the tree view tidy and easy to handle.

The folders structure may reflect the room numbers or device groups.

To create a folder:

Select “Add new folder…” from the tree view context menu.

![](https://800956157-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvyGt5xgoAU3kZytuvW1J%2Fuploads%2Fgit-blob-0e1cbd8160a74552f2b78b0149b70f3e6b17df2d%2Fimage45.png?alt=media)

A folder with a default name “New folder” is created. Change the name the way you want e.g. “**Second Floor”** and accept with Enter key. To create subfolders, create folder first and then drag and drop it into the top level folder.

Arrange the PC nodes and sensors the way you want by dragging and dropping them into the folders of your choice.

The folders structure is defined per user and is saved in a user profile.


---

# 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.boomerang3.com/boomerang-2-system-administrator-manual/tree_view/add_a_new_folder.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.