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

# No se pueden exportar las entradas

Corrija el error No entry to export en Remote Desktop Manager revisando las políticas de revelación de contraseñas y la configuración de exportación del espacio de trabajo.

No se pueden exportar entradas en Remote Desktop Manager con derechos de administrador o se recibe un mensaje de error que indica: ***No entry to export***.

### Solución

Valide todas las siguientes configuraciones y políticas para que la exportación funcione.

1. Valide que estas políticas estén desmarcadas en ***Help - Diagnostic - Policy***. Si están marcadas, consulte [Aplicar políticas](/rdm/es/knowledge-base/how-to-articles/apply-policies-gpos.md) para gestionarlas.

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

2. Valide que ***Allow reveal password for administrator and authorized users*** esté marcada en ***Administration - System Settings - Password Policy - Advanced***.
3. En ***File – Workspaces***, seleccione el espacio de trabajo y haga clic en ***Edit workspace***.
4. Valide que ***Disable reveal password*** esté desmarcada en la pestaña ***Advanced*** (no todos los espacios de trabajo tienen esta opción).


---

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