> 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/concepts/folder-structure.md).

# Folder structure

How you centrally organize the company's folders and why it is the basis of permissions.

The folder structure is the backbone of storage: you organize the company's files centrally, just like on a traditional file server, but managing it from a single place.

### Why structure comes first

It's not just about order. The folder structure is the basis on which permissions are assigned: you grant access to folders, not to individual files. That's why it's a good idea to design it with **who should see what**, usually by department or area.

> #### 📘 Design the structure with access in mind
>
> A structure by department (Accounting, Sales, Management) makes permissions almost assign themselves: each group accesses its folder.
>
> If you mix everything into a flat hierarchy, permissions quickly become a puzzle.

### Personal and shared spaces

The service distinguishes two types of space:

* **Personal space**: each user's own area.
* **Shared space**: the shared folders that more than one user or group can access, according to their permissions.

### Where to follow

* Who has access to each folder: [Users, groups, and permissions.](https://docs.plenit.com/docs-en/productos/file-storage/concepts/users-groups-and-permissions.md)
* How it's shared externally: [Access and sharing.](https://docs.plenit.com/docs-en/productos/file-storage/concepts/access-and-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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.plenit.com/docs-en/productos/file-storage/concepts/folder-structure.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.
