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

# How to Set Permissions in Your File Storage Environment

Set permissions on folders so that each user or group only accesses the content assigned to them.

Folder permissions are what ensure that each user or group accesses only the content that corresponds to them.

It is the step that protects confidential information, once you have the folder structure set up and, ideally, the groups created.

This guide shows you how to apply them.

> #### 👍 What you get
>
> Permissions defined on a folder, with the user or group and the access level you choose, extendable to its internal content.

### Before you begin

* 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 one yet, set it up with the [File Storage Quick Start.](https://docs.plenit.com/docs-en/productos/file-storage/quickstart.md)
* Have the folder structure created and, if you are going to grant access by teams, the groups prepared.

> #### 📘 The recommended order: structure, groups, permissions
>
> Permissions work best on a well-built foundation: first the [folder structure,](https://docs.plenit.com/docs-en/productos/file-storage/concepts/folder-structure.md) then the [groups](https://docs.plenit.com/docs-en/productos/file-storage/concepts/users-groups-and-permissions.md), and finally the permissions you assign here. Assigning to groups instead of to people makes management much cleaner.

### Step 1. Open the folder permissions management

In [admin.plenit.com](https://admin.plenit.com), go to **Cloud Services → File Storage** and open the subscription. Open the **Structure** tab and, in the folder you want to protect, open its **⋮** menu and go to **Permissions**. Click **Add permissions**.

![Folder permissions in Structure](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2FDkRO6XebfvHGty5vR66b%2Falmacenamiento-archivos-permisos-01.png?alt=media\&token=34d8f35f-8ff7-4eaf-a4fa-7a8f761f265f)

### Step 2. Define the permission

On the Add permissions screen:

1. Select the **users or groups** that will be able to access the folder.
2. Choose the **permission level**: **View**, **Edit** or **Total Control**.
3. Enable **Apply to subfolders and files?** if the permission should also apply to subfolders and files.
4. Press **Apply** to save.

![Permission settings for the folder](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fg1vzacRkVBhrwGUSLZLR%2Falmacenamiento-archivos-permisos-02.png?alt=media\&token=ca15ad70-c521-4acf-8481-21c575694949)

> #### 📘 What does "Apply to subfolders and files?" do?
>
> If you enable this option, the same access is also applied to the folder's subfolders and files.
>
> This is what you want to grant access to an entire area at once; leave it disabled if you only want to grant access to the first level.

To configure another folder, go back to **Structure** and repeat the process on the new location.

> #### 🚧 Grant the minimum necessary access
>
> Assign each user or group the lowest level that works for them: expanding it later is easy, but granting too much access to sensitive information is often discovered too late.
>
> Reserve full control for whoever actually manages the folder.

### Conclusion

Setting permissions means deciding, folder by folder, who can view and who can manage.

The process is short — choose the user or group, the level, and whether it applies to the internal content — but it is what turns a folder structure into an environment where information is protected.

By working with groups and giving the minimum necessary access, you keep an orderly access scheme that is easy to manage as the client grows.

### Next steps

* Review the criteria for users, groups, and permissions in [Users, groups, and permissions.](https://docs.plenit.com/docs-en/productos/file-storage/concepts/users-groups-and-permissions.md)
* Create or adjust the groups on which you apply permissions in [How to manage user groups.](https://docs.plenit.com/docs-en/productos/file-storage/how-to/how-to-manage-user-groups.md)
* Share a folder with external people in [External sharing.](https://docs.plenit.com/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 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/how-to/how-to-set-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.
