> 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/administration/user-and-security-management/users/multifactor.md).

# Multifactor

Configure the multi-factor authentication method for individual users in Devolutions Server when MFA is set to optional per user in server settings.

If you set multifactor authentication (MFA) as [***Optional per user***](/server/web-interface/administration/configuration/server-settings/security/multifactor.md) in the ***Server Settings***, you then need to configure which MFA method to use for each user.

1. In ***Administration – Users***, edit the user for whom you want to configure the MFA.
2. In the ***Multifactor*** section, select the MFA ***Type*** from the list.
3. You now have two choices. Either check ***Configure later by user*** to let the user configure their MFA by themselves when they next connect to Devolutions Server, or follow the steps to configure the MFA for the user
4. Click ***Update*** to save your changes for this user.
5. Repeat the steps for each user.

{% hint style="info" %}
MFA settings in Devolutions Server can be modified without administrator rights or approval in [***Preference –*** ***Multi-factor***.](/server/web-interface/account-menu/preferences.md#multi-factor)
{% endhint %}


---

# 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/administration/user-and-security-management/users/multifactor.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.