> 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/what-it-is.md).

# What is File Storage?

File Storage is the company’s file server, in the cloud.

Your customers save, organize, and share their files with an experience similar to Drive or OneDrive, but with the control and security of a managed environment: per-user permissions, backups included, and data in Europe.

### What distinguishes it from consumer storage

The difference is not storing files, it’s the governance you put on top.

|                 | Consumer storage          | File Storage                                         |
| --------------- | ------------------------- | ---------------------------------------------------- |
| Permissions     | Basic                     | Granular, by user, group, and folder                 |
| Backups         | Not always, or separately | Included by default                                  |
| Compliance      | Variable                  | GDPR-compliant, data in Europe                       |
| Partner control | Limited                   | Quota, users, permissions, and branding, centralized |

### How it is accessed and integrated

Files are available in three ways, which coexist:

* **Web access**, from any device.
* **Local drive**, mounted on the computer as a traditional network resource.
* **With Remote Desktop**, integrated into the environment when the customer already works there.

You have it developed in [Access and sharing.](/docs-en/productos/file-storage/concepts/access-and-sharing.md)

### What you decide and what we do

| You decide                           | We do                                       |
| ------------------------------------ | ------------------------------------------- |
| The folder structure and permissions | Operate the storage infrastructure          |
| The users and groups                 | Replicate the data in European data centers |
| The quota and usage alerts           | Run the included backups                    |
| Brand customization                  | Keep access available and encrypted         |

> #### 📘 Security by default
>
> Data is encrypted at rest and in transit, replicated in European data centers, and backed up without you having to configure anything.&#x20;
>
> Security is not an extra you activate; it comes standard.

> #### 🚧 One subscription per organization
>
> Unlike other products, an organization can only have one File Storage subscription.&#x20;
>
> We confirm it with the current platform before publishing.

### Where to go next

* Organize the folders: [Folder structure.](/docs-en/productos/file-storage/concepts/folder-structure.md)
* Grant access with control: [Users, groups, and permissions.](/docs-en/productos/file-storage/concepts/users-groups-and-permissions.md)
* Scale and protect: [Quota and backups.](/docs-en/productos/file-storage/concepts/quota-and-backups.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/what-it-is.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.
