> 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/server/knowledge-base/how-to-articles/enable-emergency-login-code-authentication.md).

# Enable emergency login code authentication

Enable emergency login code authentication in Devolutions Server so administrators can sign in by email code when other providers are unavailable.

In Devolutions Server you can enable the feature for an emergency access to allow login for administrators even if providers are down.

### Settings

{% hint style="warning" %}
Please note that a functional SMTP server is mandatory for this process.
{% endhint %}

1. In the Devolutions Server Web interface, validate that you have an email server (SMTP) configured under ***Administration – Server settings – Email***.
2. Enable the feature ***Enable emergency code authentication*** in ***Administration – Server settings – Authentication***.
3. In ***Administration – Users – General***, enable the option ***Enable emergency login*** for each administrator.

{% hint style="warning" %}
The user must be an administrator. Having administrator rights only via a ***User groups*** will not work. Each administrator will have to configure an email to receive the emergency code.
{% endhint %}

### End user experience

On login, the option to do an ***Emergency login*** will become available.

1. Click ***Emergency Login***.
2. Enter a ***Username*** and click ***Request emergency code***.

{% hint style="info" %}
For Active Directory systems, the ***Username*** must be entered following the User Principal Name (UPN) format. Meaning that the "username" is followed by the "at sign" followed by the name of the Internet domain with which the user is associated.
{% endhint %}

3. Paste the emergency code received by email, and click ***Log in***.

A log will be shown in the audit and in the administration email that an emergency login was used.


---

# 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/server/knowledge-base/how-to-articles/enable-emergency-login-code-authentication.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.