> 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/templates/default-credential-settings.md).

# Default credential settings

Edit or reset default credential settings in Remote Desktop Manager so new entries of each credential type use predefined template values.

You can access the default session settings from ***Administration – Default credential settings*** in Remote Desktop Manager.

This allows you to edit or reset your credential default settings that are used whenever a new entry is created. Every credential type is supported and can have a default template defined.

By editing your default template, you will be able to save settings that you want used at the creation of new entries.

### Settings

#### No template defined

Notice that a \[No default] notice is displayed below each credential type that does not have a default template defined.

#### Template defined

All the Credentials without the \[No default] notice has a default template. You can double-click on the type to edit the template or press the edit button.

If you wish to remove the default settings template press the delete button.


---

# 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/templates/default-credential-settings.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.