> 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/knowledge-base-articles/all-files-access-permission-denied-in-remote-desktop-manager-android.md). # All files access permission denied in Remote Desktop Manager Android Understand how the Android All Files Access permission restriction affects split view, RDP, SSH, and SFTP sessions in Remote Desktop Manager. Google has enforced stricter privacy policies, denying us the ***All Files Access*** permission. This permission is essential for several features of our application, and without it, some functionalities are either unavailable or significantly impaired. These features include: * **Split view**: This feature is no longer available for FTP, SMB, Google Drive, and Azure Blob Storage sessions. Users will not be able to browse the file structure on their local device or easily copy and move files between the device and the remote session. Only the file structure on the remote host will be visible, making file management cumbersome. * **RDP sessions**: Client file browsing from remote host: Remote hosts can no longer browse through client files on the Android device, hindering file manipulation between the remote host and the client. * **SSH sessions**: Zmodem support for uploading and downloading is no longer available. * **SFTP sessions**: Original timestamps are not preserved when downloading files. The downloaded file will have the timestamp of the actual download rather than the original file's timestamp. We apologize for any inconvenience this may cause and are committed to improving the user experience. We will also work with Google to try to regain the ***All Files Access*** permission that we previously had until it was recently revoked for reasons we are trying to figure out. --- # 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/knowledge-base-articles/all-files-access-permission-denied-in-remote-desktop-manager-android.md?ask=&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.