> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/resources/other-resources/license/renewing-your-license.md).

# Renewing your license

Renew your Devolutions license directly through the Devolutions Portal by selecting a new term and completing payment online.

Licenses can be renewed directly through the [Devolutions Portal](https://portal.devolutions.com/), provided the renewal is for the same product(s) and number of users. To switch products or modify the number of users, please contact our [sales team](mailto:service@devolutions.net) for further assistance.

1. Log in to the Devolutions Portal using the account that purchased the previous license.
2. Once logged in, go to the ***Licenses*** section. You will see a list of your active and expired licenses.
3. Find the license you wish to renew and click the ***Renew now*** button.
4. You will be able to adjust the **license term** (e.g., 1 year, 3 years). No other modifications can be made at this stage.
5. Click on ***Pay now*** to confirm your renewal.
6. Complete the payment.


---

# 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.devolutions.net/resources/other-resources/license/renewing-your-license.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.