> 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/knowledge-base/how-to-articles/vpn-groups.md).

# VPN groups

Configure VPN groups in Remote Desktop Manager so a shared VPN connection stays active until every linked session disconnects.

{% hint style="info" %}
VPN groups are defined in each entry, in the ***Connection*** – ***VPN/tunnel/gateway*** section of its properties. See [VPN/tunnel/gateway](https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/common-settings/vpn-tunnel-gateway.md).
{% endhint %}

When multiple entries are configured to use the same VPN group, they share one VPN connection, which stays active until the last of their sessions closes.

The ***VPN group*** field is available when ***Disconnect*** is set to ***On session close*** or ***Confirm disconnection***. With ***Confirm disconnection***, Remote Desktop Manager asks for confirmation only when the last session of the group closes. The field is disabled when ***Disconnect*** is set to ***Manually later***.

The VPN group name needs to be exactly the same, including uppercase and lowercase letters, to ensure that Remote Desktop Manager increments the usage counter. To reuse a name, select it in the ***VPN group*** list, which shows the names already used in the vault; to create one, type a new name or click the ***Add VPN group*** button.


---

# 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/knowledge-base/how-to-articles/vpn-groups.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.
