[Hold App/89963] [Bulk workspace edits] Add Copy Policy Settings select-workspaces page (step 1 of 3)

[fedirjh]

Explanation of Change

Adds the entry point and the first RHP step of the new "Copy settings" flow that's part of the Bulk workspace edits project. This is task 3 of the project — task 1 (scaffold #89959) is merged; task 2 (action layer #89963) is still open and this PR is stacked on top of #89963. Please land #89963 first.

What this PR adds

1. Three-dot menu entry in src/pages/workspace/WorkspacesListPage.tsx — a new "Copy settings" item with the Gear icon next to "Duplicate Workspace", visible only for admins (existing isAdmin guard). Navigates to ROUTES.POLICY_COPY_SETTINGS.

2. Select Workspaces page in src/pages/workspace/copyPolicySettings/CopyPolicySettingsSelectWorkspacesPage.tsx — first step of the RHP flow. Renders a SelectionList with MultiSelectListItem of policies the current user is admin of, with the eligibility rules from the design doc:

   • Excludes the source policy
   • Excludes policies where the user is not admin and personal policies
   • When the source is CORPORATE, only CORPORATE targets are shown (Release 1 restriction; Issue 7 lifts this in R2 with an upgrade step)

   Layout:

   • Select-all <Checkbox> above the list (indeterminate when partial)
   • <SearchBar> appears only when there are more than 12 eligible workspaces
   • "Next" persists targetPolicyIDs via setCopyPolicySettingsData (introduced in [No QA] [Bulk workspace edits] Add CopyPolicySettings action file and tests #89963) and navigates to POLICY_COPY_SETTINGS_SELECT_FEATURES; disabled until at least one workspace is selected

3. Translations — new workspace.copySettings.{title, selectWorkspaces, whichWorkspaces, searchPlaceholder, selectAll} block in all 10 language files.

4. Sentry label — CONST.SENTRY_LABEL.WORKSPACE.COPY_SETTINGS_SELECT_WORKSPACES_SELECT_ALL for the select-all pressable.

The page reads its persisted state (targetPolicyIDs) directly from ONYXKEYS.COPY_POLICY_SETTINGS so re-entry restores the user's previous selection.

Fixed Issues

$ #88669
PROPOSAL: N/A

Tests

Setup

Sign in as an admin on at least two non-personal workspaces (a mix of Team/Collect and Corporate/Control if possible).

Test 1 — Three-dot menu entry

1. Open the Workspaces list.
2. Click the three-dot menu on a workspace where you're admin.
3. Verify a new "Copy settings" item appears next to "Duplicate Workspace".
4. Verify "Copy settings" uses the Copy/duplicate icon and "Duplicate Workspace" uses the Plus icon.
5. Verify the item is not present on a workspace where you're not admin (or on personal workspaces).
6. Click "Copy settings" → the RHP slides open with the "Select workspaces" step.

Test 2 — Eligibility filtering

1. From a Corporate (Control) workspace, open Copy settings.
2. Verify the list excludes the source workspace.
3. Verify the list excludes any policy where you're not admin.
4. Verify the list excludes any personal policy.
5. Verify only other Corporate workspaces appear (Team workspaces are filtered out).
6. Go back, repeat from a Team (Collect) workspace.
7. Verify both Team and Corporate workspaces appear in the list.

Test 3 — Workspace avatars

1. Open Copy settings.
2. Verify each row shows the workspace avatar at the standard list-row size (not a tiny icon).
3. For workspaces without an avatarURL, verify the default workspace avatar (initials/colored placeholder) is rendered.

Test 4 — Select-all alignment and behavior

1. Open Copy settings.
2. Verify the select-all checkbox sits on the right of its header row, aligned with the per-row checkboxes below it.
3. Tap two rows — verify the select-all shows the indeterminate state.
4. Tap the remaining rows — verify the select-all becomes fully checked.
5. Tap the select-all checkbox — verify all rows clear.
6. Tap the select-all label/checkbox again — verify all rows toggle on.

Test 5 — Search

1. Open Copy settings on an account with 12 or fewer eligible workspaces.
2. Verify no search input is shown.
3. Open Copy settings on an account with more than 12 eligible workspaces.
4. Verify a search input appears above the select-all header (search → select-all → rows order).
5. Type part of a workspace name — verify the list filters case-insensitively.
6. Type a string that matches nothing — verify the empty state ("No results found") is shown.
7. Clear the input — verify the full list returns.

Test 6 — Next / commit selection

1. Open Copy settings.
2. With no rows selected, verify the "Next" button is disabled.
3. Select one or more rows — verify "Next" becomes enabled.
4. Click "Next" — verify the flow advances to the Select Features step (currently a stub page from this PR's scaffold).
5. In dev tools / Onyx console, verify copyPolicySettings.targetPolicyIDs now contains the selected IDs and copyPolicySettings.sourcePolicyID is set.

Test 7 — Selection cleared on RHP close

1. Open Copy settings, select 2–3 workspaces.
2. Close the RHP via the X / back button without clicking "Next".
3. Re-open Copy settings from the three-dot menu.
4. Verify the previous selection is not restored (selection is empty, "Next" disabled).

Test 8 — Console

• Verify that no errors appear in the JS console while running tests 1–7.

Offline tests

The page is a pure read of ONYXKEYS.COLLECTION.POLICY plus a useState selection; the only Onyx write happens at "Next" via setCopyPolicySettingsData. Both should work fully offline:

1. Toggle off network connectivity.
2. From the three-dot menu open Copy settings → the page renders with the cached policies, eligibility filtering still works.
3. Toggle rows / select-all → state updates instantly.
4. Click "Next" → the flow advances; verify copyPolicySettings.targetPolicyIDs is written to Onyx even while offline.
5. Re-enable network — no redundant writes are queued (selection wasn't being persisted on every toggle).

QA Steps

Same as Tests 1–8 above on the staging environment.

• 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 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

[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 ts-node ./scripts/generateTranslations.ts --help

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

[codecov]

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines	Coverage Δ
src/components/SelectionList/BaseSelectionList.tsx	64.80% <ø> (ø)
...components/SelectionList/components/ListHeader.tsx	90.00% <100.00%> (+1.76%)	⬆️
src/pages/workspace/WorkspacesListPage.tsx	72.72% <0.00%> (-0.18%)	⬇️
src/libs/actions/Policy/CopyPolicySettings.ts	86.59% <86.59%> (ø)
...ettings/CopyPolicySettingsSelectWorkspacesPage.tsx	0.00% <0.00%> (ø)
... and 147 files with indirect coverage changes