> 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/server/concepts/basic-concepts/licenses.md). # Licenses Licenses in Devolutions Server control available features and user counts, letting administrators register serials and track consumption via reports. Licenses in Devolutions Server control which features are available and how many users can access them across the deployment. Through Administration - Licenses, administrators register serials, assign them automatically or per user, and manage special license types such as workforce password management that apply at the system level rather than to individuals. Licenses themselves are purchased and renewed in Devolutions Portal, then synchronized to Devolutions Server for enforcement and reporting. A typical workflow is adding a new license after an upgrade, auto assigning it to all active users, then using reports to confirm consumption before the next renewal. #### Related topics * [Licenses](/server/web-interface/administration/user-and-security-management/licenses.md) * [Registration](/server/getting-started/installation/registration.md) * [How to renew your license](https://docs.devolutions.net/resources/other-resources/license/renewing-your-license) --- # 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/server/concepts/basic-concepts/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.