> 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/ribbon-menu-bar/administration/system-settings/user-management/user-template.md). # User template Set default values, such as offline mode, user type, license type, and default vault, applied when creating new users in Remote Desktop Manager. ***User templates*** allow you to modify the user settings that are selected by default when creating a new user in [***User management***](/rdm/ribbon-menu-bar/administration/user-management.md).

SETTINGS	DESCRIPTION
Offline mode	Defines the default setting for what users can do in Offline mode when creating a new user. Choose between Disabled (disables the Offline mode), Cache only, Read only, and Read/write.
User type	Defines the user type selected by default when creating a new user. Choose between Administrator, User, and Read-only user.
User license type	Defines the user license type selected by default when creating a new user. Choose between Default, Connection management, and Password management.
User default vault	Defines the default vault(s) for users. Select them from a vault list.
Disable user vault	Defines if the user vault is disabled or not by default when creating a new user.

--- # 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/ribbon-menu-bar/administration/system-settings/user-management/user-template.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.