Our Outcry is Heard
Summary
Salesforce is responding to community feedback on a poor user experience involving step-up authentication and dashboard errors by rolling out targeted fixes. They have already resolved dashboard errors on home pages and are patching step-up authentication to trigger more appropriately during report exports and printings rather than simple report views. While timelines for these security updates remain fluid, Salesforce is actively working to improve the user experience and reduce friction around multi-factor authentication enforcement. Salesforce professionals should watch for patches in sandboxes and stay informed via official help documentation to adapt to these evolving changes.
Takeaways
- Salesforce fixed dashboard errors caused by step-up authentication triggers.
- Step-up authentication now triggers on exporting or printing reports, not simple views.
- Use /releaseVersion.jsp appended to your org domain to quickly check patch versions.
- Timelines for multi-factor authentication changes are fluid; monitor official updates.
- Salesforce acknowledges community frustration and is working to improve UX before enforcement.
Good news! Salesforce has listened to the outcry from the community and realized that the terrible user experience I described in my last post would be disastrous. They've already rolled out some fixes that make things better and they're (at least reportedly) working on more. Timeline It would be a fool's errand for me to try to detail when particular changes are coming to your sandboxes or to production. The dates and content for security changes around phishing resistant multi factor authentication and those around step-up reporting have already changed several times, including a full delay in implementation at least once. So I can't keep up with any date changes that could be announced between when I write this, when it's published, and when you read it. As of the moment I'm typing this, the schedule for step-up authentication in production instances is "Starting July 1, 2026, staggered over approximately 30 days.