> 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/faq.md).

# Frequently Asked Questions

Each answer links to the concept, guide, or reference where the details are.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>What it is</strong></td><td>What the service is, how it differs from a consumer Drive, and when to use it instead of Objects.</td><td><a href="/pages/44ae3a156d33e0c8434705fdace2923dca88b317">/pages/44ae3a156d33e0c8434705fdace2923dca88b317</a></td></tr><tr><td><strong>Structure and permissions</strong></td><td>Where to start, how to assign access, and how inheritance works in subfolders.</td><td><a href="/pages/32bd2ea8464e87b473b24b9cfab7d920990f8dee">/pages/32bd2ea8464e87b473b24b9cfab7d920990f8dee</a></td></tr><tr><td><strong>Access and sharing</strong></td><td>Access methods, sharing with external users, and best practices.</td><td><a href="/pages/c799b7c3e5ee071a2ed20165777a29a2eedda466">/pages/c799b7c3e5ee071a2ed20165777a29a2eedda466</a></td></tr><tr><td><strong>Quota and branding</strong></td><td>Space per customer, subscriptions per organization, and brand customization.</td><td><a href="/pages/3a90fb3f6e21a7c86e7ca1a3ccae115367206c9a">/pages/3a90fb3f6e21a7c86e7ca1a3ccae115367206c9a</a></td></tr></tbody></table>

### What it is

<details>

<summary>What is File Storage?</summary>

It is the company’s file server in the cloud: your customers store, organize, and share files with an experience similar to a Drive or OneDrive, but with the control of a managed environment: user-level permissions, backups included, and data in Europe. More in [What is File Storage?](/docs-en/productos/file-storage/concepts/what-it-is.md)

</details>

<details>

<summary>How is it different from a consumer Drive or OneDrive?</summary>

The difference is not in storing files, but in the governance you add on top: granular permissions by user, group, and folder, backups included by default, GDPR compliance with data in Europe, and centralized control of quota, users, permissions, and branding.

</details>

<details>

<summary>When do I use this service and when Object Storage?</summary>

If a person is going to open and edit the file every day, it is File Storage. If software is going to write or read it (a backup, an application, a process), it is Object Storage.

</details>

### Structure and permissions

<details>

<summary>Where do I start organizing the storage?</summary>

With the folder structure, which is the foundation on which permissions are assigned: you grant access to folders, not to individual files. It is a good idea to design it with in mind who should see what, usually by department. More in [Folder structure.](/docs-en/productos/file-storage/concepts/folder-structure.md)

</details>

<details>

<summary>How do I assign access?</summary>

With users, groups, and permissions. The recommended approach is to assign permissions to groups (by department or team) instead of person by person: when someone joins or changes teams, you only update their group membership. More in [Users, groups, and permissions.](/docs-en/productos/file-storage/concepts/users-groups-and-permissions.md)

</details>

<details>

<summary>How do permissions work in subfolders?</summary>

By inheritance: everything under a folder inherits its permissions, unless you define something different in a specific subfolder. The recommendation is to give each group only the access it needs, because expanding access later is easy, and removing unnecessary access always comes too late.

</details>

### Access and sharing

<details>

<summary>How can I access files?</summary>

Through three coexisting methods: web access (from any device), a local drive mounted on the computer as a classic network resource, and integration with Remote Desktop when the customer already works in that environment. The same user can use several at the same time. More in [Access and sharing.](/docs-en/productos/file-storage/concepts/access-and-sharing.md)

</details>

<details>

<summary>Can I share files with someone outside without giving them a user account?</summary>

Yes, you generate a sharing link for a file or folder, with controls: you can add a password (so the URL alone is not enough) and an expiration date (so access closes automatically). This lets you share with a customer or supplier without opening up your environment. The details and best practices are in External sharing.

</details>

<details>

<summary>What best practices should I follow when sharing externally?</summary>

Set an expiration date whenever access is temporary, add a password when the content is sensitive (and send it through a different channel than the link), and share the folder instead of individual files when you are delivering multiple documents, removing the link when it is no longer needed.

</details>

### Quota and branding

<details>

<summary>How much space can I give a customer?</summary>

The quota goes up to 10 TB and you expand it as the customer grows. You can define usage warning thresholds (80%, 90%, 95%) to plan the increase before you run out of space. More in [Subscription and quota.](/docs-en/productos/file-storage/details/subscription-and-quota.md)

</details>

<details>

<summary>How many subscriptions can an organization have?</summary>

An organization has a single File Storage subscription. This is something we confirm with the current platform before publishing definitively.

</details>

<details>

<summary>Can I offer the service under my own brand?</summary>

Yes, you can customize the access domain (via CNAME), the logo, colors, favicon, and SSL certificate, so your customer accesses an environment with your identity and not a generic one. The service warns you before the certificate expires. More in [Customization.](/docs-en/platform/organizations/detalles/customization.md)

</details>

### Next steps

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Quick Start</strong></td><td>Deploy the service step by step.</td><td><a href="/pages/e75644491156154e8205a4b1eb266ff1f62d5e16">/pages/e75644491156154e8205a4b1eb266ff1f62d5e16</a></td></tr><tr><td><strong>Concepts</strong></td><td>Understand the service design decisions.</td><td><a href="/pages/af63359f6bc4faac58f07c9bdb05aa1776a3b46f">/pages/af63359f6bc4faac58f07c9bdb05aa1776a3b46f</a></td></tr><tr><td><strong>How-to</strong></td><td>Step-by-step guides for working with file storage.</td><td><a href="/pages/6ab0b0eb15fb25a9fbe1750cdf300b0967d78b16">/pages/6ab0b0eb15fb25a9fbe1750cdf300b0967d78b16</a></td></tr><tr><td><strong>Details</strong></td><td>Quota, permissions, and sharing.</td><td><a href="/pages/20d102679235b93474cd92bdce3c7b21ce442e86">/pages/20d102679235b93474cd92bdce3c7b21ce442e86</a></td></tr></tbody></table>


---

# 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/faq.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.