Salesforce is enforcing MFA - here's what it means for your dashboards

Salesforce has started requiring multi-factor authentication for all users logging directly into a Salesforce org, rolling out gradually across customers through September 3, 2026. If you haven't seen any change yet, you likely will as the rollout reaches your org.

👉 See the announcement

The part that affects Fugo: when an account has no MFA method registered, Salesforce now defaults to prompting for a passkey — a Face ID, Touch ID, Windows Hello, or security-key credential tied to one device. Fugo can't authenticate with passkeys yet, so if the account your Salesforce dashboard uses gets steered into that flow, its automated sign-in will get stuck and the dashboard will stop refreshing.

The good news: this is easy to avoid. If you (or the service account you use for Fugo) see a "Create a Passkey" screen, click Choose Another Verification Method and register a TOTP-based authenticator app instead — that's the same secret-key method Fugo already supports today.

👉 More details are in our Salesforce Dashboard App Guide.

If you sign into Salesforce via Okta or Google SSO, you may not be affected at all. We're actively working on adding passkey support to Dashboards, so this workaround for Salesforce (and other apps that adopt passkey-based MFA) won't be necessary going forward.

Need help adjusting or creating your Salesforce dashboards? Reach out to us in the support chat or via support@fugo.ai.