> 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/getting-started/managing-credentials.md). # Managing credentials Depending on your organization's security policies, there are several methods for handling credentials. We support a wide range of scenarios, with the most popular listed below. It is important to note that these credentials are used for connecting to remote hosts, not for launching Remote Desktop Manager Windows. {% hint style="info" %} Some of the following options are not available in the Free edition of Remote Desktop Manager, as they rely on features provided by [advanced workspaces](https://docs.devolutions.net/rdm/workspaces/workspace-types/native-workspaces/?tab=macos). {% endhint %} ### Key points Below are a few key points that the solution administrator must be aware of:

Key points	Description
Password visibility	You can store passwords in a credentials entry (username/password entry). By default, the password is stored in encrypted form and is masked in the interface. This makes the password usable for connections without exposing it directly. Depending on the credentials entry type and the user’s permissions, the password may or may not be viewable (for example, by clicking the "eye" icon). Multiple credentials entry types are provided. It is important to choose the type carefully based on administrative and security needs.
Credentials set on folders	Folders can have defined credentials, useful for reusing the same credentials across a branch of the network infrastructure. To use these, child sessions must be adjusted to use inherited credentials.
Entry location	Storing entries in the tree view allows users with View permissions on that entry (or folder by inheritance) to use them, enabling credential sharing with team members. A user vault is available for storing personal information privately. These credentials can still be accessed publicly by referencing them or through User-specific settings.
User-specific settings	User-specific settings provide partial overrides for entry settings, including credentials. Overrides allow selecting credentials directly or linking to credentials stored elsewhere, like in the user vault.

### Common scenarios Here are the most common scenarios and their resolutions. In most cases, the preferred approach is for sessions to use inherited credentials. This allows the session to traverse up the hierarchy until it finds a set of credentials—whether they are defined, linked, or overridden at a higher level.

SCENARIO	STRATEGY
One set of credentials is used by all of the staff, be it for the whole system or for a branch in your tree view (customer, department, etc.).	Set the credentials on the vault settings. All children use inherited credentials.
Each user has their own credentials for many different branches (often corresponding to customers/departments, etc.).	Make use of the user-specific settings on each branch. All children use inherited credentials.
Each user has its own credentials managed by an administrator.	This solution involves a little more work. The administrator must create a folder for each user, then grant permissions only to that user. The user will then use user-specific settings to specify that the credentials stored in that folder are used to override what is defined in the entries.
Each team uses the same credentials.	As above, but all team members have access to the folder. They all have to use the user-specific settings.
Each user uses their domain account.	Configure sessions to use My personal credentials. Each user will be prompted to define them once per workstation that they use.

--- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.devolutions.net/rdm/getting-started/managing-credentials.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.