> For the complete documentation index, see [llms.txt](https://docs.b2copy.b2broker.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.b2copy.b2broker.com/admin-guide/register-new-back-office-users/disable-2fa-for-back-office-users.md).

# Disable 2FA for Back Office users

Disabling 2FA via email codes for Back Office users is only recommended if you have a standalone B2COPY solution without an SMTP server, as emails can’t be sent in this case.

To disable 2FA for a user:

{% stepper %}
{% step %}
Go to **System** > **Users** > **Users**.
{% endstep %}

{% step %}
Select the user and click the **Edit** button.

For users with 2FA enabled via email codes, **Email** is displayed in the **Two-Factor Authentication** column on the **Users** page.

<figure><img src="/files/18qqzqvDJffm6jfr7FdL" alt="Two-Factor Authentication column – Email"><figcaption><p>Two-Factor Authentication column – Email</p></figcaption></figure>
{% endstep %}

{% step %}
On the **Edit user** page, click the **Actions** button in the upper-right page corner, and then select **Disable 2FA** in the dropdown.

<figure><img src="/files/xW1TGeVrsBwctE5dgEw3" alt="Disable 2FA"><figcaption><p>Disable 2FA</p></figcaption></figure>
{% endstep %}

{% step %}
Confirm the action in the displayed popup.
{% endstep %}

{% step %}
Click **Save** to apply the changes.
{% endstep %}
{% endstepper %}

For the user, **Disabled** is now displayed in the **Two-Factor Authentication** column on the **Users** page.

<figure><img src="/files/6J2VdLz7oX16DrwmQp76" alt="Two-Factor Authentication column – Disabled"><figcaption><p>Two-Factor Authentication column – Disabled</p></figcaption></figure>

‍After disabling 2FA, you can securely provide the credentials to the newly registered user so they can sign in to the Back Office.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.b2copy.b2broker.com/admin-guide/register-new-back-office-users/disable-2fa-for-back-office-users.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.