> For the complete documentation index, see [llms.txt](https://docs.patchmypc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patchmypc.com/patch-my-pc-cloud/manage/settings/subscription/license/request-additional-licenses.md).
# Request Additional Patch My PC Cloud Licenses
*Applies to: Patch My PC Cloud*
If you determine you need additional licenses for your Patch My PC (PMPC) Cloud subscription, these can be requested as follows:
1. Navigate to **Settings | Subscription**
2. Under your current plan, click **Request More**
{% hint style="info" %}
**Note**
If you have less than 90 days remaining on your subscription, you will be unable to request additional licenses to add to your current subscription. Instead, the text on the button will show as **Request a Quote** and you should [request a quote](/patch-my-pc-cloud/manage/settings/subscription/license/request-quote.md) for a new subscription to include the increased number of devices.
{% endhint %}
3. On the **Request Devices** screen, verify your email address, then increase the number of devices you are currently licensed for to the required number, then click **Send Request**
4. Click **Close** on the **Request Sent** screen.
---
# 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.patchmypc.com/patch-my-pc-cloud/manage/settings/subscription/license/request-additional-licenses.md?ask=&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.
