> 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?

The company's cloud file server: folders, permissions, and access from anywhere, with backups included.

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: user-based permissions, backups included, and data in Europe.

### What sets it apart from consumer storage

The difference isn't 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 through three coexisting access methods:

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

It is developed in [Access and sharing.](https://docs.plenit.com/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 | Operating the storage infrastructure      |
| Users and groups                     | Replicating data in European data centers |
| Quota and usage alerts               | Running the included backups              |
| Brand customization                  | Keeping 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.
>
> Security isn't an extra you turn on; it comes standard.

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

### Where to follow

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