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

# Impossibile esportare le voci

Risolva l'errore No entry to export in Remote Desktop Manager verificando i criteri di rivelazione delle password e le impostazioni di esportazione dello spazio di lavoro.

Impossibile esportare le voci in Remote Desktop Manager con diritti di amministratore oppure viene visualizzato il messaggio di errore: ***No entry to export***.

### Soluzione

Convalidi tutte le seguenti impostazioni e criteri affinché l'esportazione funzioni.

1. Verifichi che questi criteri non siano selezionati in ***Help - Diagnostic - Policy***. Se sono selezionati, veda [Applicare i criteri](/rdm/it/knowledge-base/how-to-articles/apply-policies-gpos.md) per gestirli.

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

2. Verifichi che ***Allow reveal password for administrator and authorized users*** sia selezionato in ***Administration - System Settings - Password Policy - Advanced***.
3. In ***File – Workspaces*** selezioni lo spazio di lavoro e clicchi su ***Edit workspace***.
4. Verifichi che ***Disable reveal password*** non sia selezionato nella scheda ***Advanced*** (non tutti gli spazi di lavoro dispongono di questa opzione).


---

# 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/it/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.