> 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/troubleshooting-articles/unable-to-export-entries.md).

# Unable to export entries

Fix the No entry to export error in Remote Desktop Manager by reviewing reveal password policies and workspace export settings.

Unable to export entries in Remote Desktop Manager with administrator rights or receiving error message stating: ***No entry to export***.

### Solution

Validate all the following settings and policies for the export to work.

1. Validate that these policies are unchecked in ***Help - Diagnostic - Policy*** If they are checked, see [Apply policies](/rdm/knowledge-base/how-to-articles/apply-policies-gpos.md) to manage them.

* ***Disable the reveal password feature***
* ***Remove possibility to see passwords entirely***

2. Validate that ***Allow reveal password for administrator and authorized users*** is check in ***Administration - System Settings - Password Policy - Advanced***.
3. In ***File – Workspaces*** select the workspace and click ***Edit workspace***.
4. Validate that ***Disable reveal password*** is unchecked in the ***Advanced*** tab (not all workspaces have this option).


---

# 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/troubleshooting-articles/unable-to-export-entries.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.