> 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 The folder structure is the skeleton of storage: you organize company 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. Folder structure is the foundation on which permissions are assigned: you grant access to folders, not to individual files. That's why it should be designed with **who should see what**, usually by departments or areas. > #### 📘 Design the structure with access in mind > > A department-based structure (Accounting, Sales, Management) makes permissions almost self-assigning: each group accesses its folder. > > If you mix everything into a flat hierarchy, permissions later become a puzzle. ### Personal and shared spaces The service distinguishes two types of space: * **Personal space**: each user's own area. * **Shared space**: the common folders that more than one user or group can access, according to their permissions. ### Where to go next * Who accesses each folder: [Users, groups, and permissions.](/docs-en/productos/file-storage/concepts/users-groups-and-permissions.md) * How it is shared externally: [Access and sharing.](/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 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/concepts/folder-structure.md?ask=&goal= ``` `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.