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

# Quick Start

Deploying File Storage takes three steps: you create the subscription with its quota, associate the users who will use it, and check access.&#x20;

The folder structure and permissions are defined later.

> #### 📘 What you get
>
> A deployed File Storage environment, with its quota set and its associated users, ready for you to start organizing folders and permissions.&#x20;
>
> Each organization has its own File Storage subscription.

### Before you begin

* Be logged in to the Plenit platform.

### Start the signup process

Depending on whether you already work with the service or it is your first time, you reach the wizard through one of these routes. All three end up in the same place.

| Situation                               | How you start                                                                                               |
| --------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
| You already use File Storage            | Go into the service and click **New subscription**, at the top right of the list                            |
| It is your first time using the service | On the product page, click **I want to try it now**                                                         |
| From a specific customer                | Go to **Organization › Subscriptions** and choose **File Storage** under "What do you want to sign up for?" |

<figure><img src="/files/1397d074b74c93cbad4de6f2e5887daba19174bf" alt=""><figcaption><p><em>From the service list you can see the usage of all subscriptions</em></p></figcaption></figure>

<figure><img src="/files/77c91a897998d7f098594ca65efb0aff052a8674" alt=""><figcaption><p><em>The first time, you enter the same wizard from the product page</em></p></figcaption></figure>

If you start from the service list, you first choose the **organization** where you deploy the service and continue with **Next**.

<figure><img src="/files/1a14af85d7e204ce9e69fa67da34bd84a9ece855" alt=""><figcaption></figcaption></figure>

### Step 1. Create the subscription and set the quota

In the wizard:

1. Enter the **subscription name**, which will help you identify it.
2. Define the **storage quota** with the slider (starting from 25 GB). As you move it, you can see the estimated cost per month and per hour. You can increase it later if the customer grows.
3. Move on to the next step.

<figure><img src="/files/d73eb45a010063dc7b3fe51d9f8dc4ab6d28c233" alt=""><figcaption><p><em>Name the subscription and adjust the quota with the slider</em></p></figcaption></figure>

> #### 📘 Consumption alert to be adjusted later
>
> The consumption notification threshold (default, 90%) is managed in the **Quota** tab of the subscription, along with the quota itself. You can see it in Quota and backups.

### Step 2. Associate the users

Select the users who will use the service. If someone is missing, you can add them on the spot with **New user** and their email address.&#x20;

When you click **Save**, we create the service.

<figure><img src="/files/20a983a91a0089243dc982591aee617e25347f1a" alt=""><figcaption><p><em>Step 2. Associate the users who will use the service, or create a new one on the spot.</em></p></figcaption></figure>

When you save, we start preparing the subscription.&#x20;

Provisioning takes a few minutes.

<figure><img src="/files/c8787cbbe760ffa557204de03ed76d4b2ff25fa0" alt=""><figcaption></figcaption></figure>

### Step 3. Check access

The service appears as a **card in the panel**, with its usage and its action menu (Details, Delete).

<figure><img src="/files/cdd40a3ab73777df69a89b007920493b1822c2fd" alt=""><figcaption><p><em>Once deployed, the subscription appears as a card in the panel, with its usage and its action menu.</em></p></figcaption></figure>

When you enter the subscription you have the service tabs (Summary, Quota, Users, Groups, Structure, Customization) and the button **Connect**, with the access links. This allows users to enter the environment even if you have not yet defined the folder structure.

<figure><img src="/files/caf465170b2abfc8397e2102bd9d53d05087ecb9" alt=""><figcaption><p><em>When you enter the subscription you have the Connect button with the access links, even if you have not yet set up the folders.</em></p></figcaption></figure>

> #### 📘 Automatic notifications
>
> When the service is provisioned, we send you a confirmation, and each new user receives a welcome email. You do not have to notify anyone yourself.

### You already have storage deployed

From here, the next thing is to shape it:

* Organize the folders, from the **Structure**: [Folder structure.](/docs-en/productos/file-storage/concepts/folder-structure.md)
* Grant access with control, from **Users** and **Groups**: [Users, groups, and permissions.](/docs-en/productos/file-storage/concepts/users-groups-and-permissions.md)
* Mount the drive locally or access it via the web, with **Connect** and **Customization**: [Access and 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/quickstart.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.
