> 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-admin-guide/v19-en-us/parallels-ras-19-administrators-guide/user-device-management-and-client-policies/configuring-remote-file-transfer/configure-file-transfer-for-a-client-policy.md).

# Configure file transfer for a client policy

To configure remote file transfer for a client policy, do the following:

1. In the RAS Console, select the **Policies** category.
2. Right-click a desired policy in the right pane and choose **Properties**.
3. In the left pane, navigate to **Session** > **Local devices and resources**.
4. Select the **File transfer** node.
5. In the right pane, select one of the following in the **Allow file transfer** drop-down list:
   * **Client to server only**: Transfer files from client to server only.
   * **Server to client only**: Transfer files from server to client only.
   * **Bidirectional**: Transfer files in both directions.

For additional information about client policies, see [**Client Policies**](/landing/ras-admin-guide/v19-en-us/parallels-ras-19-administrators-guide/user-device-management-and-client-policies/client-policies.md)**.**


---

# 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 dynamically 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-admin-guide/v19-en-us/parallels-ras-19-administrators-guide/user-device-management-and-client-policies/configuring-remote-file-transfer/configure-file-transfer-for-a-client-policy.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 `build a script that syncs our docs to a CMS` 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.