> 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/users-groups-and-permissions.md).

# Users, groups, and permissions

How you grant access by user and group, and how granular permissions with inheritance keep information under control

Access control relies on three pieces that work together: users, groups, and permissions. Understanding how they fit together is what saves you work and prevents unauthorized access.

### Users

Each person accesses with their identity, managed from the platform. Sign-in can be done with their credentials or with their email, depending on what you prefer.

### Groups

A group brings together several users to grant them access all at once. It is the unit that simplifies everything: instead of giving permissions person by person, you give them to the group and maintain access by department or team.

### Granular permissions

Permissions are assigned to users and groups on folders, and are propagated downward by **inheritance**: anything under a folder inherits its permissions, unless you define something different.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2FSxos37xXbFsoh0uLi2O6%2Fdiagram-file-storage-permission-inheritance.png?alt=media&amp;token=9b43f346-5398-4085-bfad-4be07533159b" alt="Diagrama de herencia de permisos: el grupo Comercial tiene lectura y escritura sobre la carpeta; la subcarpeta Propuestas hereda y Confidencial rompe la herencia con una excepción solo para Dirección"><figcaption><p>You assign permissions to a group on the folder; subfolders inherit, unless you define an exception</p></figcaption></figure>

| You assign to | For                                          |
| ------------- | -------------------------------------------- |
| User          | Specific cases or individual access          |
| Group         | The usual case: access by department or team |

> #### 📘 Work with groups and least privilege
>
> Assign permissions to groups, not people: when someone joins or changes teams, you only move their group membership.
>
> And give each group the minimum access it needs; expanding later is easy, removing too much access always comes too late.

### Where to continue

* What permissions are assigned to: [Folder structure.](https://docs.plenit.com/docs-en/productos/file-storage/concepts/folder-structure.md)
* How it is shared with external parties: [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/users-groups-and-permissions.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.
