> 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/da/knowledge-base/knowledge-base-articles/understand-remote-desktop-manager-licensing.md).

# Forstå licensering af Remote Desktop Manager

Forstå, hvordan licensering af Remote Desktop Manager fungerer pr. bruger og ikke pr. installation, og hvem der kan være dækket af en enkelt licens.

I forbindelse med licensering er en bruger en person, der bruger Remote Desktop Manager. Legitimationsoplysninger, der er gemt i Remote Desktop Manager, har ingen indflydelse på licenseringen.

Licenser beregnes pr. bruger, ikke pr. installation. Der er ingen begrænsning på at installere Remote Desktop Manager (bærbar, stationær, hjemmecomputer osv.), så længe De har det rette antal licenser til hver person, der opretter forbindelse til Deres system.

Licenserne er til brug for den kunde, der står på fakturaen. De kan ikke dele Deres licens med en underleverandør eller, i tilfælde af en tjenesteudbyder, med dennes kunder. Det gælder, selv hvis De giver dem adgang til et Team-arbejdsområde.

Kontakt [vores salgsafdeling](mailto:sales@devolutions.net) for at beskrive Deres scenarie, få hjælp til, hvilken licens De skal købe, og få et tilbud.


---

# 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/da/knowledge-base/knowledge-base-articles/understand-remote-desktop-manager-licensing.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.