[Due for payment 2025-12-08] SAML-"Require SAML login" toggle is not greyed out when toggling it in offline mode

[nlemma]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: v9.2.65-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #74973
Email or phone of affected tester (no customers): applausetester+agadmin@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Windows 11/ Chrome, Samsung S23FE/ Chrome, iPhone 13 Mini/ iOS 26.1
App Component: Other

Action Performed:

1. Navigate to https://staging.new.expensify.com/
2. Log in with an account that is a domain admin
3. Go to the “Workspaces” tab
4. Tap on the three-dot menu in the domain applause.expensifail.com > Go to domain > SAML
5. Go Offline
6. Tap on the "Require SAML login" toggle

Expected Result:

The "Require SAML login" toggle is greyed out when toggling it.

Actual Result:

The "Require SAML login" toggle is not greyed out when toggling it.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug7014925_1764253789760.require_SAML_toggle.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @JmillsExpensify

[melvin-bot]

Triggered auto assignment to @JmillsExpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[melvin-bot]

Triggered auto assignment to @lakchote (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[lakchote]

@mhawryluk will take a look at the issue. I don't think this should be a blocker given this is offline, and a minor bug.