[Payment due @truph01] Add Auto-categorize new expenses workspace setting to let strict admins disable auto-categorization"

[dukenv0307]

Explanation of Change

Add Auto-categorize new expenses workspace setting to let strict admins disable auto-categorization

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/669240
PROPOSAL:

Tests

Test case 1:

1. Go to WS -> Category -> More -> Settings
2. Verify that: Auto-categorize new expenses is shown and enabled by default
3. Verify that we can disable/enable it
4. Create an expense in that WS without category
5. Verify that the category is missing if Auto-categorize new expenses is disabled and the category is added automatically when Auto-categorize new expenses is enabled

Test case 2: Verify the changelog in admin room when disbale/enable auto-cateogrize

1. Go to staging.new.expensify.com
2. Go to workspace settings > Categories > Settings.
3. Disable and enablel Auto-categorize new expenses.
4. Go to #admins.
5. Verify that the changelog for auto-categorisation settings will appear in #admins.

Test case 3: Workspace - Auto categorization settings will be disabled in the duplicated workspace if the original one has been disabled

1. Go to staging.new.expensify.com
2. Go to workspace settings > Categories > Settings.
3. Disable Auto-categorize new expenses.
4. Go back to workspace list.
5. Click 3-dot menu on the workspace > Duplicate workspace > Next > Continue.
6. Open duplicated workspace settings > Categories.
7. Click Settings.
8. Verify that: auto categorization settings are disabled in the duplicated workspace.

Test case 4: Expense - Expense isn't auto categorized after disabling auto categorisation

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Create an expense with category.
4. Go to workspace settings > Categories > Settings.
5. Disable Auto-categorize new expenses.
6. Go to workspace chat.
7. Create an expense with the same merchant in Step 3 and without category.
8. Open the expense.
9. Verify that: The new expense will not be auto categorized.

• Verify that no errors appear in the JS console

Offline tests

Same as above

QA Steps

Same as above

• 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 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 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 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)
• 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.
• 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-09-02.at.13.26.10.mov

Screen.Recording.2026-09-03.at.10.54.49.mov

Screen.Recording.2026-09-07.at.11.48.17.mov

[melvin-bot]

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

1. Look at the code and make sure there are no malicious changes.
2. Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx bun ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx bun ./scripts/generateTranslations.ts --compare-ref main

[codecov]

Codecov Report

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

Files with missing lines	Coverage Δ
src/CONST/index.ts	91.52% <ø> (ø)
...c/components/ReportActionItem/MoneyRequestView.tsx	82.06% <100.00%> (ø)
src/libs/API/types.ts	100.00% <ø> (ø)
src/libs/ReportAlternateTextUtils.ts	87.15% <100.00%> (+0.07%)	⬆️
src/libs/ReportNameUtils.ts	81.62% <100.00%> (+0.72%)	⬆️
src/libs/TransactionUtils/index.ts	93.18% <100.00%> (+0.86%)	⬆️
...x/report/actionContents/PolicyChangeLogContent.tsx	100.00% <100.00%> (ø)
...s/workspace/categories/WorkspaceCategoriesPage.tsx	78.35% <100.00%> (+1.05%)	⬆️
src/libs/ReportActionsUtils.ts	81.85% <83.33%> (+0.30%)	⬆️
...es/inbox/report/ContextMenu/ContextMenuActions.tsx	40.44% <50.00%> (+0.08%)	⬆️
... and 2 more
... and 392 files with indirect coverage changes

[melvin-bot]

@abzokhattab 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]

[melvin-bot]

I could not review this diff, so I did not approve the workflow runs. An Expensify employee will review it and approve them manually.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: dd1b3fd606

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[melvin-bot]

I could not review this diff, so I did not approve the workflow runs. An Expensify employee will review it and approve them manually.

[dukenv0307]

@truph01 could you please review it?

[truph01]

@dukenv0307 Could you address this #100115 as well?

[dukenv0307]

@truph01 I don't think we should do it here since it's still reproducible after revert in #100115 (comment)

[truph01]

@dukenv0307 I think policy.glCodes is undefined for that test account, so the setting option isn't shown because there is no data to display. So, this test result is expected.

However, after our PR, the "auto-categorize" option is always shown, then this test result is unexpected.

Also, in this PR, we're removing shouldBeBlocked={shouldBlockEmptySettings} from src/pages/workspace/categories/DynamicWorkspaceCategoriesSettingsPage.tsx.

[truph01]

Test case 2: Verify the changelog in admin room when disbale/enable auto-cateogrize

@dukenv0307 Could you verify this test? I don't see any changelog when disbale/enable auto-cateogrize

[truph01]

@dukenv0307

In the test case titles, could you update them to describe the expected behavior rather than the bug?

Instead of:

Test case 3: Workspace - Auto categorization settings is not disabled in the duplicated workspace

Please use:

Test case 3: Workspace - Auto categorization settings will be disabled in the duplicated workspace if the original one has been disabled

And instead of:

Test case 4: Expense - Expense is auto categorized after disabling auto categorisation

Please use:

Test case 4: Expense - Expense isn't auto categorized after disabling auto categorisation

[truph01]

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 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 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 and each prop has a /** comment above it */
  • The file is named correctly
  • 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
  • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
  • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
  • All JSX used for rendering exists in the render method
  • 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 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 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

Screen.Recording.2026-08-26.at.12.22.00.mov

Android: mWeb Chrome

Screen.Recording.2026-08-26.at.12.22.46.mov

iOS: HybridApp

Screen.Recording.2026-08-26.at.12.15.23.mov

iOS: mWeb Safari

Screen.Recording.2026-08-26.at.12.14.25.mov

MacOS: Chrome / Safari

Screen.Recording.2026-09-15.at.10.15.14.mov

[dukenv0307]

cc @huult. I'm working on it

[melvin-bot]

I could not review this diff, so I did not approve the workflow runs. An Expensify employee will review it and approve them manually.

[dukenv0307]

@truph01

#100248 (comment): fixed
#100248 (comment): fixed

[truph01]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Already looking forward to the next diff.

Reviewed commit: 639033b8cc

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[melvin-bot]

🎯 @truph01, thanks for reviewing and testing this PR! 🎉

A payment issue will be created for your review once this PR is deployed to production.
E/E issue linked to the PR - https://www.github.com/Expensify/Expensify/issues/669240.

If payment is not needed (e.g., regression PR review fix etc), react with 👎 to this comment to prevent the payment issue from being created.

[truph01]

@dukenv0307 Can we ask QA to test the adhoc build here?

[dukenv0307]

Can we ask QA to test the adhoc build here?

@truph01 Agree 👍. @heyjennahay can you help ^?

[github-actions]

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

[heyjennahay]

I have just run the ad hoc build

[github-actions]

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

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-305b0c3-d890fbf-19619c98bb2d192dc81a03feda7ae90f4751a899/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-305b0c3-d890fbf-1a12a6363ca467e9764d96d20da94c1b85184dd6/index.html

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

---

👀 View the workflow run that generated this build 👀