> 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/use-multiple-edge-website-entries-with-different-credentials-in-remote-desktop-manager.md).

# Usar varias entradas de sitio web de Edge con distintas credenciales en Remote Desktop Manager

Utilice varias entradas de sitio web de Microsoft Edge con credenciales diferentes en Remote Desktop Manager asignando nombres de perfil únicos.

Es posible utilizar varias entradas de sitio web de Edge que usen cada una credenciales diferentes. Mediante el uso de ***Nombres de perfil***, resulta posible tener un determinado perfil cualquier número de veces, haciendo que cada uno sea único o repitiéndolo tantas veces como sea necesario.

1. Acceda a las ***Propiedades*** de una entrada de ***Sitio web***.
2. Asegúrese de que la opción ***Mostrar*** esté establecida en ***Integrado (con pestañas)*** , o puede que estos pasos no funcionen.
3. Establezca la opción ***Navegador web*** en ***Microsoft Edge***, en la pestaña ***Común*** – ***General*** – ***General***.
4. Introduzca la URL del sitio web deseado.
5. Vaya a la pestaña ***Avanzado***.
6. Marque la opción ***Nombre de perfil*** e introduzca un nombre.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Tenga en cuenta que los perfiles de Remote Desktop Manager son específicos de Remote Desktop Manager y no están relacionados con los perfiles del navegador Edge.</p></div>
7. Haga clic en ***Aceptar*** para guardar los cambios y cerrar la ventana.


---

# 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/use-multiple-edge-website-entries-with-different-credentials-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.
