> 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/platform/accounts/how-to/how-to-manage-subscriptions.md).

# How to Create and Manage Your Subscriptions

Subscriptions are the unit with which you organize and bill services. 

From **Subscriptions** you create them, query them, and manage them, both yours and your clients'.

> #### 📘 **What will you learn?** 
>
> Know where you can see your subscriptions, how to contract a new one and how to edit it, check its usage, or delete it.

### Before you begin

You need to be logged in and have permission to manage subscriptions. There are two paths, and each shows the subscriptions differently:

* **From Home (your global view)** — in **Home > Subscriptions** you see the **list** of all your subscriptions, in tabs **My subscriptions** and **clients**.
* **From an organization** — in **Organization > Subscriptions** you see those of that organization in **cards**, one per service, with their live metrics.

It is the same place with two presentations: the list is for managing in bulk; the cards are for seeing the status of an organization at a glance.

### The two views

#### The list (Home)

In **Home > Subscriptions** you have the list, with a **Filter** and these columns:

* **Name** — the subscription name.
* **Service** — the service type.
* **Created** — the creation date.
* **Actions** — the menu **⋮** of each subscription.

The tab **My subscriptions** shows those of your organization; the tab **clients** gathers those of the organizations you manage, with additional columns (Organization, Licenses, Zones, and Version) and the status of each one.

![Home > Subscriptions, list view](/files/087db1fd854ac41e3c043de9379c70a33810e4d6)

#### The cards (Organization)

In **Organization > Subscriptions** you see one card per service of that organization, with its live metrics: Servers (cores and RAM), Remote Desktop (sessions and applications), File and Object Storage (GB, quota, and usage percentage), DNS (zones and records), and Disaster Recovery (plan and replica). Each card has its own menu **⋮**.

![Organization > Subscriptions, card view](/files/167b8528417951d2da86677a4866d4d9a5804205)

### Create a subscription

1. In **Subscriptions**, click **New subscription**.
2. In **What do you want to contract?**, choose the service: Servers, Remote Desktop, Disaster Recovery, File Storage, Object Storage, DNS, or Software Licenses.
3. From there you follow the deployment flow for that service.

![What do you want to contract?, the service selector](/files/67722bb4f459a4fb9def552fda48e3f95e3cec7d)

> #### ❗️ **It is created in the selected organization**
>
> The subscription is created in the organization you have selected at that moment, whether you enter from Home or from an organization. Before contracting, check above that it is the correct organization.

> #### 🚧 **Organization selector** 
>
> A selector is planned to choose the organization during sign-up. Until then, the subscription goes to the one you have selected.

The deployment of each service, with all its steps and options, is explained in its own Quick Start, within that service's documentation.

### Manage a subscription

The actions menu (**⋮**) changes depending on the tab you are in, because the tasks are not the same in your subscriptions as in your clients'.

#### In My subscriptions

The **⋮** brings **Edit**, **Usage** and **Delete**.

* **Edit** — opens the edit screen: you change the **Name** of the subscription (the Service and creation date are shown as reference, they are not editable) and save.
* **Usage** — takes you to the consumption for that subscription, within your [Billing](https://claude.ai/chat/facturacion), where you see consumption and invoices.
* **Delete** — cancels the subscription.

![My subscriptions, actions menu with Usage](/files/250f14fd3017e7406f169e778c587499191c1cc3)

#### In client subscriptions

The **⋮** brings **Edit**, **Update** and **Delete**.

* **Edit** — same as in your subscriptions.
* **Update** — applies an available update to that client subscription.
* **Delete** — cancels the subscription.

![Client subscriptions, actions menu with Update](/files/3d20ae49ce2f32cd80c57ca086dc80b5e18e49ff)

#### Update a client subscription

When an update is available, **Update** opens a notice that first **validates some requirements** to ensure that it is viable on all servers of the subscription: the number of snapshots, the connection with the servers, and the installed software versions. 

If everything is correct, you confirm with **Update**.

![Requirements validation before updating](/files/b99b4e0539552fd3250ef524725720b33222008e)

> #### 🚧 **During the update there are restarts**
>
> When applying the update, the servers restart several times. It is advisable to avoid user connections until the process finishes.

#### Delete a subscription

**Delete** opens a confirmation modal that warns that all associated data will be deleted and that the action cannot be undone. To confirm, you will have to type **DELETE**.

![Confirmation when deleting a subscription](/files/c7441eae923187bc62bd13b2c1049a96835aae50)

> #### ❗️ **Irreversible action** 
>
> Deleting a subscription permanently deletes all its data.

### Conclusion

Now you know where your subscriptions are, how the list view and the card view differ, how to contract a new one and how to edit, update, or delete it. The details of each service live in its own documentation.

### Next steps

* Check usage and invoices in [Billing.](/docs-en/platform/billing.md)
* See what each column in the list shows in[ The lists.](/docs-en/platform/accounts/details/lists.md)
* To deploy a specific service, go to its Quick Start in the service documentation.


---

# 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/platform/accounts/how-to/how-to-manage-subscriptions.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.