> 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/details/permissions.md).

# Permissions

This is the reference for how access is structured.

The why and best practices are in [Users, groups, and permissions.](/docs-en/productos/file-storage/concepts/users-groups-and-permissions.md)

### Who you assign permissions to

| Level | What for                                     |
| ----- | -------------------------------------------- |
| User  | Individual access or specific cases          |
| Group | The usual case: access by department or team |

### What they are applied to and how they propagate

| Aspect      | Detail                                                                           |
| ----------- | -------------------------------------------------------------------------------- |
| Scope       | Permissions are assigned to folders                                              |
| Inheritance | Anything under a folder inherits its permissions                                 |
| Exception   | You can define a different permission in a subfolder and break inheritance there |

### Spaces

| Space    | What it is                                                           |
| -------- | -------------------------------------------------------------------- |
| Personal | Each user's personal area                                            |
| Shared   | Folders shared by multiple users or groups, depending on permissions |

> #### 📘 Work with groups
>
> Assigning permissions to groups instead of people keeps access organized: adding or moving someone boils down to changing their group, without touching folder by folder.

### Where to go next

* What they are assigned to: [Folder structure.](/docs-en/productos/file-storage/concepts/folder-structure.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/details/permissions.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.