> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/ras-user-portal-guide/v21/running-remote-applications-and-desktops/using-drag-and-drop-functionality.md).

# Using drag and drop functionality

Parallels User Portal supports drag and drop functionality when running remote applications and desktops.

Here's how to use drag and drop when working with a remote application:

1. Select a file on your local computer.
2. Drag and drop the selected file to an app. The 'Save as' window will pop up.
3. Enter a name for the file and save it. The file will be saved on the server hosting the app.

You can also drag and drop files between two remote apps running on different hosts.

Here's how to use drag and drop with a remote desktop:

1. Select a file on your local computer.
2. Drag and drop the selected file to a remote desktop. The 'save as' window will pop up.
3. Enter a name for the file and save it. The file will be saved on the desktop on the server that hosts it.


---

# 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.parallels.com/landing/ras-user-portal-guide/v21/running-remote-applications-and-desktops/using-drag-and-drop-functionality.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.