> For the complete documentation index, see [llms.txt](https://helpdesk.augmentt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdesk.augmentt.com/configuration/enabling-2fa-for-portal-users.md).

# Enabling 2FA for Portal Users

Two-factor authentication adds a second verification step to Augmentt portal logins, on top of your username and password. Enabling it applies at the MSP organization level, so it protects every user who logs into your Augmentt tenant.

{% hint style="info" %}
This setting controls login security for the **Augmentt portal itself** — it's separate from the M365/Duo MFA posture monitoring Augmentt performs for your *clients*. If you're looking for how Augmentt tracks your clients' MFA compliance, see [DUO Integration](/configuration/duo-integration.md) and the M365 permissions article ([M365 Integration & Permissions](/configuration/m365-integration-and-permissions.md)).
{% endhint %}

## Where to find it

1. Log in to the Augmentt portal at [app.augmentt.com](https://app.augmentt.com).
2. In the left-hand navigation, click **Configuration**, then **Companies**.
3. Find your MSP tenant — this is the **Organization** company in the company list, not one of your client companies.
4. Click the vertical ellipsis (**⋮**) on the far right of that row.

{% hint style="warning" %}
This action is scoped to your Organization row specifically. Enabling it here applies the setting system-wide across your MSP tenant, not just to the user you're currently logged in as.
{% endhint %}

## What this affects

| Scope               | Effect                                                                                  |
| ------------------- | --------------------------------------------------------------------------------------- |
| Organization row    | 2FA requirement applies to all portal users in your MSP tenant                          |
| Client company rows | Not applicable — 2FA for portal access is an Organization-level control, not per-client |

{% hint style="warning" %}
The exact toggle label and any enrollment/re-authentication flow a user sees the next time they log in were not available to verify in this session — confirm the current wording and step count in the live portal before publishing screenshots or exact click paths.
{% endhint %}

## Common issues

**A user needs their 2FA/MFA reset.** This happens most often when someone loses their authenticator device or gets a new phone. Support can clear a user's registered authentication method so they can re-enroll — if you hit an error stating a method "matches the user's current default authentication method and cannot be deleted," that means another authentication method needs to be set as default first before the old one can be removed. If self-service clearing is unavailable, contact <support@augmentt.com>.

**Distinguish portal 2FA from client MFA posture alerts.** If you're seeing alerts like "Disable weakest 2FA authenticators" in Secure, that's a posture check against your *client's* M365 tenant authentication methods (SMS, Voice Call, Email OTP) — not the Augmentt portal login setting on this page. Don't confuse the two when troubleshooting.


---

# 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://helpdesk.augmentt.com/configuration/enabling-2fa-for-portal-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.