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

# Use multiple Edge website entries with different credentials in Remote Desktop Manager

Use multiple Microsoft Edge website entries with different credentials in Remote Desktop Manager by assigning unique profile names.

It is possible to use multiple Edge website entries that each use different credentials. By using ***Profile names***, it makes it possible to have a certain profile any number of times, making each unique or repeating it as many time as needed.

1. Go into the ***Properties*** of a ***Website*** entry.
2. Make certain the ***Display*** option is set to ***Embedded (tabbed)*** , or these steps may not work.
3. Set the ***Web browser*** option to ***Microsoft Edge***, in the ***Common*** – ***General*** – ***General*** tab.
4. Input the desired website URL.
5. Go to the ***Advanced*** tab.
6. Check the ***Profile name*** option and input a name.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Note that Remote Desktop Manager profiles are specific to Remote Desktop Manager and not related to Edge browser profiles.</p></div>
7. Click ***OK*** to save the changes and close the window.


---

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