> 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/cloud/concepts/basic-concepts/licenses.md). # Licenses Devolutions Cloud licenses centralize registration and seat assignment for products like Remote Desktop Manager, Devolutions Gateway, and Password Manager. The ***Licenses*** section in Devolutions Cloud centralizes registration and assignment of Devolutions product licenses so administrators can see who is entitled to which tools. After registering license keys for products such as Remote Desktop Manager, Devolutions Password Manager, or Devolutions Gateway, administrators can assign seats to individual users from Administration – Licenses. Because licensing is tied to Devolutions Cloud, deprovisioning a user or revoking their access also revokes their application entitlement. A typical workflow is to register a Remote Desktop Manager license once in Devolutions Cloud and then assign it to new team members along with vault access, ensuring their client activates automatically the first time they connect. #### Related topics * [Register product licenses](/cloud/web-interface/administration/management/licenses/register-product-licenses.md) * [Assign product licenses](/cloud/web-interface/administration/management/licenses/register-product-licenses/assign-product-licenses.md) * [License](https://docs.devolutions.net/resources/other-resources/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/cloud/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.