> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/productos/file-storage/how-to/how-to-structure-folders-in-windows.md).

# How to Structure Your Folders in Windows

The folder structure is the foundation on which you organize your client’s storage and, later, assign permissions. This guide shows you how to create it from the panel: first the main folders, then the subfolders inside each one.

> 👍 What you get
>
> The organization’s folder structure is set up and ready to start saving files and applying permissions by folder.

### Before you start

* Access the administration panel at [admin.plenit.com](https://admin.plenit.com) with permissions on the service.
* Have an active **File Storage** subscription. If you don’t have it yet, set it up with the [File Storage Quick Start.](/docs-en/productos/file-storage/quickstart.md)
* Having decided on the organization’s main folders (for example, HR, Finance, or Projects).

> #### 📘 The structure is the basis of permissions
>
> It is advisable to design the folders with in mind who should see what, usually by department, because permissions are assigned on folders. The criterion for designing it is in [Folder structure.](/docs-en/productos/file-storage/concepts/folder-structure.md)

### Step 1. Open the Structure section

In [admin.plenit.com](https://admin.plenit.com), go to **Cloud Services → File Storage** and enter the subscription. Open the **Structure** and start the process from there.

{/\* 📸 SCREENSHOT 1 · Structure tab · start of folder creation \*/}

![Structure section of File Storage](https://REEMPLAZA-URL/almacenamiento-archivos-estructura-01.png)

### Step 2. Create the main folders

Type the folder name and create it. To add another at the same level, click **New folder** and repeat. With this, you have the first level of the structure.

{/\* 📸 SCREENSHOT 2 · creation of a main folder · New folder button \*/}

![Creation of the main folders](https://REEMPLAZA-URL/almacenamiento-archivos-estructura-02.png)

### Step 3. Create subfolders inside each folder

Enter a main folder (for example, HR), click **Create folder**, type the subfolder name, and create it. Use **New folder** to repeat as many times as needed.

{/\* 📸 SCREENSHOT 3 · creation of subfolders inside a main folder \*/}

![Creation of subfolders inside a folder](https://REEMPLAZA-URL/almacenamiento-archivos-estructura-03.png)

### Step 4. Repeat in the rest of the areas

Apply the same procedure in each main folder until the organization’s structure is complete. When you finish, the shared space is ready to store and share files.

> #### 🚧 Creating folders does not apply permissions
>
> The structure organizes the information, but it does not limit who can view or edit each folder. To control access, configure the permissions when you finish the structure, in [Users, groups, and permissions.](/docs-en/platform/organizations/detalles/users.md)

### Conclusion

Setting up the structure is a simple, repetitive process: you create the main folders, go into each one, and add its subfolders.

The important thing is the prior design, because permissions are later assigned on these folders: a good structure by department makes granting and removing access clean and easy.

Remember that creating folders does not protect anything by itself; access control is the next step.

### Next steps

* Review the criteria for designing the structure in [Folder structure.](/docs-en/productos/file-storage/concepts/folder-structure.md)
* Share folders with external people in [External sharing.](/docs-en/productos/file-storage/details/external-sharing.md)


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.plenit.com/docs-en/productos/file-storage/how-to/how-to-structure-folders-in-windows.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.