[Due for payment 2025-08-20] Expensify Card - Workflows toggle is locked for new workspace when Expensify Card is not enabled

[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: 9.1.90-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp https://test-management.browserstack.com/projects/2219752/test-runs/TR-115/folder/13176890/41237379/827411178
Email or phone of affected tester (no customers): applausetester+070808kh@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Workspace Settings

Action Performed:

Precondition:

• Workspace is set up with Expensify Card feature.
• Workspace is upgrade to Control plan (important).

1. Go to staging.new.expensify.com
2. Go to workspace settings > Expensify Card.
3. Click Issue card.
4. Select your account > Next.
5. Select virtual card.
6. Enter amount > Next.
7. Select Smart limit > Next (Important).
8. Complete the rest of the flow.
9. After assigning card, create a new workspace. (The new workspace will be in Control plan by default).
10. Go to workspace settings > More features.
11. Click on the locked toggle on Workflows row.
12. Click Go to Expensify Cards.

Expected Result:

In Step 11, the Workflows row for the new workspace will not have a locked toggle because Expensify Card feature is not enabled on the new workspace.

Actual Result:

In Step 11, the Workflows row for the new workspace shows a locked toggle when Expensify Card feature is not enabled on the new workspace.
In Step 12, when Go to Expensify Cards is clicked, nothing happens.

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

Bug6910071_1754549550277.20250807_144557.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @mallenexpensify

[melvin-bot]

Triggered auto assignment to @mallenexpensify (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.

[melvin-bot]

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

[melvin-bot]

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

[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.