> 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/organizations/detalles/subscriptions.md).

# Subscriptions

The two states of the section: the catalog to deploy and the cards for active subscriptions.

The section **Subscriptions** shows the services of that organization.

It has two states: the catalog for deploying new services and the view of active subscriptions with their metrics.

### Deploy a service

When the organization does not yet have a service, or when you want to add one, you will see the catalog: one card per service with a button **Deploy** and a link **More information**. Available services include Servers, Remote Desktop, File Storage, Object Storage, DNS, Disaster Recovery and, from Marketplace, Licenses. The subscription details for each service are in its own documentation.

### Active subscriptions

With contracted services, each subscription is shown as a card with its live metrics and an actions menu (⋮). Depending on the service, you will see:

| Service           | Metrics shown                                                                                                                                                                 |
| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Servers           | Cores and GB of RAM, with the percentage of usage per server. Includes a carousel with CPU/RAM usage, primary and secondary space, and network traffic (upload and download). |
| Remote Desktop    | Sessions and Applications, with active user sessions.                                                                                                                         |
| File Storage      | GB and Users, with the percentage in use over the total.                                                                                                                      |
| Object Storage    | Quota and Accesses, with the percentage in use.                                                                                                                               |
| DNS               | Zones and Records, with the total number of requests.                                                                                                                         |
| Disaster Recovery | Plan and GB, with the replica status.                                                                                                                                         |

> #### 📘 **Management is shared with your account**
>
> Creating, editing, updating, or deleting a subscription is done the same way as from Home.
>
> You have the steps in [How to create and manage your subscriptions.](https://docs.plenit.com/docs-en/platform/accounts/how-to/how-to-manage-subscriptions.md)

### Next steps

* Review the other sections of the panel in [Details.](https://docs.plenit.com/docs-en/platform/organizations/detalles.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/platform/organizations/detalles/subscriptions.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.
