> 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/rdm/es/knowledge-base/knowledge-base-articles/understand-remote-desktop-manager-licensing.md). # Comprender las licencias de Remote Desktop Manager Comprenda cómo funcionan las licencias de Remote Desktop Manager por usuario en lugar de por instalación, y a quién puede cubrir una sola licencia. En el contexto de las licencias, un usuario es una persona que utiliza Remote Desktop Manager. Las credenciales almacenadas en Remote Desktop Manager no tienen ningún impacto en las licencias. Las licencias se calculan por usuario, no por instalación. No existe ninguna limitación para instalar Remote Desktop Manager (portátil, ordenador de sobremesa, ordenador doméstico, etc.), siempre que disponga del número adecuado de licencias para cada persona que se conecte a su sistema. Las licencias son para uso del cliente que aparece en la factura. No puede compartir su licencia con un subcontratista ni, en el caso de un proveedor de servicios, con los clientes de este. Esto se aplica incluso si les concede acceso a un espacio de trabajo Team. Póngase en contacto con [nuestro departamento de ventas](mailto:sales@devolutions.net) para describir su escenario, obtener ayuda sobre qué licencia adquirir y conseguir un presupuesto. --- # 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/rdm/es/knowledge-base/knowledge-base-articles/understand-remote-desktop-manager-licensing.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.