> For the complete documentation index, see [llms.txt](https://buildsystem.eintosti.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://buildsystem.eintosti.de/v4/getting-started/creating-a-folder.md).

# Organizing Folders

To keep the world navigator clean, worlds can be organized inside virtual directories called **Folders** and highlighted using **Pinned Worlds**.

***

## World Folders

Folders categorize worlds within the Navigator (Public, Private, or Archive tabs).

### Creating a Folder

1. Open the Navigator (`/worlds`).
2. Navigate to the desired category tab.
3. Click the **Birch Wood Skull** button (requires permission `buildsystem.create.folder`).
4. Type the folder name in chat and press Enter.

### Managing Folders via Commands

| Operation            | Command                                              | Permission                         | Description                                                                           |
| -------------------- | ---------------------------------------------------- | ---------------------------------- | ------------------------------------------------------------------------------------- |
| **Add World**        | `/worlds folder <folder> add <world>`                | `buildsystem.folder.add`           | Places a world inside a folder. A world can only reside in one folder at a time.      |
| **Remove World**     | `/worlds folder <folder> remove <world>`             | `buildsystem.folder.remove`        | Removes a world from its folder.                                                      |
| **Delete Folder**    | `/worlds folder <folder> delete`                     | `buildsystem.folder.delete`        | Deletes the folder. Can only be done if the folder is empty of worlds and subfolders. |
| **Set Permission**   | `/worlds folder <folder> setPermission <permission>` | `buildsystem.folder.setpermission` | Restricts access to all worlds inside this folder.                                    |
| **Set Project**      | `/worlds folder <folder> setProject <name>`          | `buildsystem.folder.setproject`    | Tags all worlds inside this folder with a project name.                               |
| **Set Display Item** | `/worlds folder <folder> setItem <Material>`         | `buildsystem.folder.setitem`       | Sets the item representing the folder in the GUI.                                     |

{% hint style="info" %}
If enabled in `config.yml` (`override-permissions` and `override-projects`), worlds automatically inherit their parent folder's permissions and project names. Once removed, they revert to their previous standalone values.
{% endhint %}

***

## Pinned Worlds (New in 4.0.0)

Pinned Worlds allow administrators to force specific worlds to always display at the top of navigator lists, bypassing the player's active sorting configuration.

### Behavior

* **Priority Sorting**: Pinned worlds are sorted above all unpinned worlds in the navigator, regardless of whether the active sort is alphabetical, by project, status, or date.
* **Prefix Indicator**: Pinned worlds display a configurable prefix before their names in menus.
* **Management**: Can be toggled on or off from the world's **Edit Menu** (right-click the world in `/worlds` or use `/worlds edit`).

### Requirements

* **Permission**: `buildsystem.edit.pin` (default: false, must be explicitly granted).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://buildsystem.eintosti.de/v4/getting-started/creating-a-folder.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.