> 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/rdp-session-entry/enable-super-pan-in-an-rdp-entry.md).

# Enable super pan in an RDP entry

Enable super pan in an RDP entry in Remote Desktop Manager to auto scroll a full screen remote desktop by pointing at the window border.

Specifies or retrieves a Boolean value that indicates whether SuperPan is enabled or disabled. Super pan is a feature that allows a user to easily navigate a remote desktop in full-screen mode, when the dimensions of the remote desktop are larger than the dimensions of the current client window. Instead of using scroll bars to navigate the desktop, the user can point to the window border, and the remote desktop will scroll automatically in that direction.

{% hint style="info" %}
SuperPan does not support more than one monitor.
{% endhint %}

The ***Enable super pan*** option can be found under ***Properties*** – ***Common*** – ***General*** – ***Advanced***. It is not enabled by default.

{% hint style="info" %}
Learn more about [super pan](https://learn.microsoft.com/en-us/windows/win32/termserv/imsrdpclientadvancedsettings7-enablesuperpan).
{% endhint %}


---

# 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/rdp-session-entry/enable-super-pan-in-an-rdp-entry.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.