> 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/web-interface/authentication-login.md).

# Authentication login

Sign in to the Devolutions Server web interface using Microsoft, Domain, Okta, or Devolutions Server credentials, including emergency login access.

To connect to the Devolutions Server ***Web interface***, users will need to choose an authentication method. The authentication methods available for login will depend upon the administrator authentication type setup made in ***Administration - Server settings - Authentication***.

{% hint style="info" %}
Follow this [link](/server/web-interface/administration/configuration/server-settings/general/authentication.md) to learn on how to set an authentication type.
{% endhint %}

#### User authentication

1. Open a web browser and navigate to the URL of the Devolutions Server instance.
2. Choose your authentication method between Microsoft, Domain, Okta or Devolutions Server user.

{% hint style="info" %}
The [Emergency login](/server/knowledge-base/how-to-articles/enable-emergency-login-code-authentication.md) is a feature that needs to be enabled to allow an emergency access login for administrators even if providers are down (Azure or AD).
{% endhint %}

3. Enter the ***Username*** and ***Password*** of the chosen authentication method to connect.

{% hint style="success" %}
Click ***Choose your authentication method*** to go back to the list of authentication types.
{% endhint %}

4. Click ***Sign in***.


---

# 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/web-interface/authentication-login.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.