> 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-manage-user-groups.md).

# How to Manage User Groups in File Storage

User groups let you assign permissions to several accounts at once, instead of one by one.

You group people by department, team, or role, and give access to the group: when someone joins or changes teams, you just move their group membership.

This guide shows you how to create them.

> #### 👍 What you get
>
> A user group created with its members, ready to assign permissions collectively and save you from configuring account by account.

### Before you start

* 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 it yet, set it up with the [Quick Start for File Storage](/docs-en/productos/file-storage/quickstart.md).
* Have the users you are going to add to the group already registered.

> #### 📘 Why work with groups
>
> Assigning permissions to groups instead of people reduces errors and speeds up setup: you grant access once to the group and manage joins and leaves by moving the person between groups, without touching each folder's permissions. 
>
> The criterion for organizing them is in [Users, groups, and permissions.](/docs-en/productos/file-storage/concepts/users-groups-and-permissions.md)

### Step 1. Open the Groups section

In [admin.plenit.com](https://admin.plenit.com), go to **Cloud Services → File Storage** and enter the subscription. Open the **Groups** menu **New group**.

{/\* 📸 SCREENSHOT 1 · Groups tab · New group button \*/}

![Groups section with the New group button](https://REEMPLAZA-URL/almacenamiento-archivos-grupos-01.png)

### Step 2. Fill in the group details

In the form:

* Enter the **group name**.
* Add a **short description** that identifies its purpose.
* Select the **users** who will be part of the group.

Click **Save**.

{/\* 📸 SCREENSHOT 2 · form · name, description, and user selection \*/}

![Group creation form](https://REEMPLAZA-URL/almacenamiento-archivos-grupos-02.png)

> #### 🚧 If you don't see users to add
>
> You can only add users to the group who have already been registered. If the list appears empty or someone is missing, register those people first and then create the group again.

### Step 3. Check that the group has been created

The group appears in the list of **My Groups**, with its name, description, and associated users. To create another one, click **New group** and repeat the process.

{/\* 📸 SCREENSHOT 3 · My Groups list with the created group \*/}

![Group created in the My Groups list](https://REEMPLAZA-URL/almacenamiento-archivos-grupos-03.png)

### Conclusion

Creating a group is quick — name, description, and members — but its value lies in what it saves you afterward: instead of giving permissions person by person, you give them to the group once, and joins and leaves are managed by moving people between groups.

By organizing them by department or role from the start, keeping access orderly stops being a headache.

### Next steps

* Use the group to assign access in [Users, groups, and permissions.](/docs-en/productos/file-storage/concepts/users-groups-and-permissions.md)
* Design which folders these permissions apply to in [How to create the folder structure.](/docs-en/productos/file-storage/concepts/folder-structure.md)
* Share folders with external people in [External sharing.](/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 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/how-to/how-to-manage-user-groups.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.