> 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/knowledge-base-articles/entry-settings/lockself-password-manager.md). # LockSelf password manager Configure the LockSelf password manager entry in Remote Desktop Manager to launch sessions using stored LockSelf credentials securely. Use LockSelf credentials directly in Remote Desktop Manager connections without exposing passwords. Launch sessions without copying or revealing sensitive data.


SETTINGS	DESCRIPTION
Name	The name of the entry. This field is required.
Folder	The folder where the entry is located.

### General

SETTINGS	DESCRIPTION
Use "My account settings"	Use the LockSelf credentials configured in File – My account settings – LockSelf, under Password management. When this option is checked, Base URL, Authorization token, and LS token are unavailable. This option is hidden when the policy that disables My account settings is applied.
Base URL	Enter the base URL of the LockSelf instance. Required unless Use "My account settings" is checked.
Authorization token	Store the X-Auth-Token. The information can be found in the user management section of LockSelf. Required unless Use "My account settings" is checked.
LS token	Store the X-Ls-Token. The information can be found in the user management section of LockSelf. Required unless Use "My account settings" is checked.
Credential	Select credentials stored in LockSelf. Click the ellipsis button (...) to choose from the list. Required unless Always prompt with list is checked, in which case this field is unavailable.
Always prompt with list	When this option is checked, the entry prompts users upon use with a list of credentials to choose from.

--- # 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/knowledge-base-articles/entry-settings/lockself-password-manager.md?ask=&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.