Workspace - Created workspace automatically set to "Control" if default is also "Control"

[jponikarchuk]

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.3.64-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/test-runs/TR-23127/folder/13177080/41237924/1372513785?p=2
#86301
Email or phone of affected tester (no customers): ibellicotest+2250@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Motorola MotoG60 / Android 12 (Hybrid app) - Windows 11 / Chrome
App Component: Workspace Settings

Action Performed:

1. Open the staging.new.expensify.com website.
2. Sign up with a new account.
3. Complete onboarding modal selecting "Track and budget expenses"
4. Navigate to "Workspace" > "Overview" > "Plan Type"
5. Upgrade to "Control" plan.
6. Return to "Workspaces"
7. Click on "New Workspace" > "Confirm"
8. Note that the new workspace plan type is automatically set to "Control"

Expected Result:

New created workspaces should be automatically set to "Collect" plan.

Actual Result:

Second created workspace is automatically set to "Control" plan if default workspace is already in a "Control" plan type.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Video.mp4

View all open jobs on GitHub

[melvin-bot]

@stitesExpensify recently merged #86301, but they are OOO right now, so I'll auto-assign someone else.

[melvin-bot]

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

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

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

[OSBotify]

Investigation Summary

Classification: Frontend bug
Causing PR: #86301 - "follow up: default new WS to Control if user is in annual subscription" by @daledah (High confidence)
Related Issues: #65697

Recommendation: REVERT

PR #86301 introduced a regression where any new workspace is defaulted to "Control" plan for users on an annual subscription, regardless of intent. The fix is in the App repo (frontend), and the PR can be cleanly reverted.

Assigned: @daledah (PR author), @stitesExpensify (approving reviewer), @Ollyws (approving reviewer) from causing PR
Labels: DeployBlockerCash kept (Frontend bug, App deploy blocked). No label changes made.

Detailed Analysis

Evidence

• The issue body explicitly links to PR follow up: default new WS to Control if user is in annual subscription #86301 as the causing PR.
• The melvin-bot comment also flags PR follow up: default new WS to Control if user is in annual subscription #86301 as recently merged by @stitesExpensify.
• PR follow up: default new WS to Control if user is in annual subscription #86301 was merged on 2026-04-21 and is included in the current staging deploy (version 9.3.64-0).
• The bug is reproducible on staging but not on production, confirming it was introduced in this staging cycle.

Verification

• The affected area is workspace creation defaulting to the wrong plan type.
• PR follow up: default new WS to Control if user is in annual subscription #86301 modifies three files directly related to workspace creation:
  • src/pages/workspace/WorkspaceConfirmationPage.tsx — reads privateSubscription?.type and passes isAnnualSubscription flag
  • src/libs/actions/App.ts — threads the isAnnualSubscription param through createWorkspaceWithPolicyDraftAndNavigateToIt and savePolicyDraftByNewWorkspace
  • src/libs/actions/Policy/Policy.ts — uses isAnnualSubscription to override workspace type to CORPORATE in both buildPolicyData and createDraftInitialWorkspace

Root Cause

PR #86301 checks privateSubscription?.type === CONST.SUBSCRIPTION.TYPE.ANNUAL in WorkspaceConfirmationPage. This condition becomes true as soon as a user is on any annual subscription (e.g., after upgrading their first workspace to Control). As a result, every subsequent new workspace also gets defaulted to CONST.POLICY.TYPE.CORPORATE ("Control") because the subscription check is account-level, not per-workspace. New workspaces should default to CONST.POLICY.TYPE.TEAM ("Collect") unless explicitly chosen otherwise.