migrate WORKSPACE_DOWNGRADE

[huult]

Explanation of Change

Fixed Issues

$ #83831
PROPOSAL:

Tests

Same QA step

• Verify that no errors appear in the JS console

Offline tests

QA Steps

Preconditions:

• Have a workspace on the Control plan.

1. Open the Expensify app.
2. Go to Workspace > Overview > Plan type.
3. Select Collect, then click Save.
4. Verify that the Workspace Downgrade page opens correctly and that you can navigate back normally.

• Verify that no errors appear in the JS console

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I verified there are no new alerts related to the canBeMissing param for useOnyx
• I followed proper code patterns (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
  • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
• I verified that if a function's arguments changed that all usages have also been updated correctly
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
• If new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

Screen.Recording.2026-07-29.at.13.21.44.mov

[melvin-bot]

@suneox Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

[codecov]

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines	Coverage Δ
src/SCREENS.ts	100.00% <ø> (ø)
src/libs/Navigation/linkingConfig/OldRoutes.ts	100.00% <ø> (ø)
src/libs/Navigation/linkingConfig/config.ts	66.66% <ø> (ø)
...scriptionPlan/SubscriptionPlanCardActionButton.tsx	0.00% <ø> (ø)
...workspace/DynamicWorkspaceOverviewPlanTypePage.tsx	0.00% <ø> (ø)
src/ROUTES.ts	22.65% <0.00%> (ø)
...gation/AppNavigator/ModalStackNavigators/index.tsx	6.42% <0.00%> (ø)
...kspace/downgrade/DynamicWorkspaceDowngradePage.tsx	0.00% <0.00%> (ø)
... and 10 files with indirect coverage changes

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 94ce5db292

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[suneox]

Manual test cases base on current code change

---

DYNAMIC_ROUTES.WORKSPACE_DOWNGRADE — Downgrade workspace from Control → Collect (Team)

Precondition (shared): test account owns at least one Control plan workspace (guard canModifyPlan; otherwise NotFoundPage renders). The Downgrade page is an RHP modal.

---

Case 1.1 — Workspace Overview → Plan type → Collect → downgrade (policyID from base path)

Target: DynamicWorkspaceOverviewPlanTypePage.tsx:125

Precondition: user owns one Control workspace (this is the PR's QA flow).

Steps:

1. Open the app and log in (owner of one Control workspace).
2. Go to Workspaces → select the Control workspace → Overview.
3. Tap Plan type.
4. Select Collect, then tap Save.
5. Verify the Workspace Downgrade page opens (RHP), URL suffix .../overview/plan/downgrade.
6. Verify the downgrade content renders (not NotFoundPage) → policyID resolved from the base path (no query param at this call site).

Expected: Downgrade page opens correctly with valid workspace policyID.

---

Case 1.2 — Settings → Subscription → plan card → downgrade (policyID via query param)

Target: SubscriptionPlanCardActionButton.tsx:85

Precondition: user owns one Control workspace; on the Subscription screen. Call site passes policy?.id → URL carries ?policyID=<id>.

Steps:

1. Open the app and log in.
2. Go to Settings → Subscription.
3. On the plan card (or the Compare plans modal), tap the action button that leads to downgrade (Collect/Team).
4. Verify the Workspace Downgrade page opens (RHP), URL .../subscription/downgrade?policyID=<id>.
5. Verify the page shows the workspace matching policyID (not NotFoundPage) → query param passed correctly.

Expected: Downgrade page opens with the correct policyID from the query param.

---

Case 1.3 — Policy-less downgrade → "Go to Workspaces" button (!policyID branch)

Target: DowngradeIntro.tsx:114

Precondition: reach the downgrade page without a policyID (!policyID branch) — e.g. from Subscription when policy?.id is undefined. Shows the multi-workspace note + a Go to Workspaces button.

Steps:

1. Reach the downgrade page in the no-policyID state.
2. Verify the UI shows the multi-workspace note + Go to Workspaces button.
3. Tap Go to Workspaces.
4. Verify navigation to the Workspaces list (forceReplace).
5. Go back → verify it returns to the base path (suffix downgrade stripped, does not fall back to Home).

Expected: Button works; back path is correct (subscription/base, not Home).

---

Case 1.4 — Legacy deep-link redirect (OldRoutes backward-compat)

Target: OldRoutes.ts (downgrade entries) — tests in getMatchingNewRouteTest.ts

Precondition: logged in. Paste the legacy URL directly into the address bar (web) or open it as a deep-link.

Steps (run each legacy URL, verify the redirect):

1. /workspaces/<policyID>/downgrade/ → redirects to /workspaces/<policyID>/overview/plan/downgrade?policyID=<policyID> → downgrade page opens, policyID preserved.
2. /workspaces/<policyID>/downgrade (no trailing slash) → redirects to the same as (1).
3. /workspaces/downgrade (policy-less) → redirects to /settings/subscription/downgrade → downgrade page (policy-less).
4. Verify the new routes are NOT redirected again: open /workspaces/<id>/overview/plan/downgrade and /settings/subscription/downgrade → stay as-is, no loop.

Expected: all three legacy links redirect to the correct new destination (policyID kept in path/query); new routes have no false-positive.

---

Case 1.5 — Back nav & refresh restore stack

Target: DynamicWorkspaceDowngradePage goBack + useDynamicBackPath

Precondition: on the downgrade page (from Case 1.1 or 1.2).

Steps:

1. On the downgrade page (before downgrading), tap the header back arrow.
2. Verify it returns to the correct entry screen (plan page or subscription), URL suffix downgrade removed.
3. Cold refresh a URL with the suffix .../overview/plan/downgrade → verify the stack restores correctly (entry screen below, downgrade modal above), no /not-found.
4. Cold refresh /settings/subscription/downgrade → verify it restores correctly under Subscription.

Expected: back returns to the correct base; refresh restores the full stack (thanks to the goBack(backPath) fallback + entryScreens).

---

[huult]

You can review this PR. The failing tests are unrelated to the changes in this PR.

[suneox]

Reviewer Checklist

• I have verified the author checklist is complete (all boxes are checked off).
• I verified the correct issue is linked in the ### Fixed Issues section above
• I verified testing steps are clear and they cover the changes made in this PR
  • I verified the steps for local testing are in the Tests section
  • I verified the steps for Staging and/or Production testing are in the QA steps section
  • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
• I checked that screenshots or videos are included for tests on all platforms
• I included screenshots or videos for tests on all platforms
• I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
• I verified tests pass on all platforms & I tested again on:
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
• I verified proper code patterns were followed (see Reviewing the code)
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I verified that this PR follows the guidelines as stated in the Review Guidelines
• I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
• If a new component is created I verified that:
  • A similar component doesn't exist in the codebase
  • All props are defined accurately
  • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
  • The only data being stored in the state is data necessary for rendering and nothing else
  • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
• I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp

Android: mWeb Chrome

iOS: HybridApp

iOS: mWeb Safari

MacOS: Chrome / Safari

DYNAMIC_ROUTES.WORKSPACE_DOWNGRADE — Downgrade workspace from Control → Collect (Team)

CleanShot.2026-07-30.at.12.56.22.1.mp4

---

Case 1.1 — Workspace Overview → Plan type → Collect → downgrade (policyID from base path)

---

Case 1.2 — Settings → Subscription → plan card → downgrade (policyID via query param)

---

Case 1.3 — Policy-less downgrade → "Go to Workspaces" button (!policyID branch)

---

Case 1.4 — Legacy deep-link redirect (OldRoutes backward-compat)

---

Case 1.5 — Back nav & refresh restore stack

---

[suneox]

LGTM. The unit test is still failing on the latest main

[mjasikowski]

@huult merge main and we'll be good to go

[huult]

done

[huult]

cc @mjasikowski

[github-actions]

🚧 mjasikowski has triggered a test Expensify/App build. You can view the workflow run here.

[OSBotify]

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

[github-actions]

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #97307.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-5f1f5862479-49926c7-ae8ee3afc85e54eb4be1167316555e84ca461865/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-5f1f586-49926c7-f3214a3d4415915b45a08427133ce2f75c4944aa/index.html

Web 🕸️
https://97307.pr-testing.expensify.com

---

👀 View the workflow run that generated this build 👀