> 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/troubleshooting-articles/non-admin-users-are-unable-to-view-passwords.md).

# Non-admin users are unable to view passwords

Let non-administrator users view and copy passwords in Remote Desktop Manager by granting the View password permission on the vault, folders, or entries.

Users who are not administrators cannot view or copy the passwords of entries.

### Solution

For security reasons, viewing passwords is a permission that must be granted explicitly. To allow users or user groups to view the passwords of all the entries in a vault:

1. Go to ***Administration*** – ***Vault settings*** – ***Security*** – ***Inherited permissions***.
2. Set the permissions to ***Custom***.
3. Grant the ***View password*** permission to the users or user groups that need it.
4. Click ***OK*** to save.

Depending on your security policies, you may want to apply more granular settings. You can also set the ***View password*** permission in ***Security*** – ***Permissions*** in the properties of a folder or an entry.

#### Related articles

* [Batch grant access](/rdm/ribbon-menu-bar/administration/system-settings/vault-management/default-permissions/batch-grant-access.md)
* [Permissions](/rdm/user-group-based-access-control/permissions.md)

#### See also

* [Devolutions Academy – Managing entry permissions](https://academy.devolutions.net/student/page/1925085-managing-entry-permissions?curriculum_activity_id=2667180\&path_id=1925039\&sid=aae472b5-2471-497d-8258-9836fd752366\&sid_i=1)


---

# 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/troubleshooting-articles/non-admin-users-are-unable-to-view-passwords.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.