> 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/how-to-articles/configure-an-access-code-entry-in-remote-desktop-manager.md).

# Configurar una entrada de código de acceso en Remote Desktop Manager

Configure una entrada de código de acceso en Remote Desktop Manager para ofrecer a los usuarios una interfaz simplificada para ver y copiar contraseñas.

El ***código de acceso*** es una entrada de credencial que ofrece una interfaz simplificada a los usuarios, proporcionando únicamente las acciones ***Ver contraseña*** y ***Copiar contraseña***.

{% hint style="info" %}
La configuración de la entrada ***Código de acceso*** también es válida para Remote Desktop Manager macOS.
{% endhint %}

1. Vaya a la bóveda del espacio de trabajo en la que desea crear la ***entrada de código de acceso*** en el ***panel de navegación***.
2. Seleccione ***Código de acceso*** en ***Nueva entrada – Gestión de credenciales – General***.
3. Asigne un nombre a la entrada y seleccione su carpeta.
4. Elija una contraseña y haga clic en ***OK*** para cerrar la ventana.

***Ver contraseña*** y ***Copiar contraseña*** ya están disponibles en el ***panel*** en ***Acciones***.


---

# 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/how-to-articles/configure-an-access-code-entry-in-remote-desktop-manager.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.