[No QA] Docs updates for E/A#100291 bulk action bar replaces Selected dropdown

[MelvinBot]

Explanation of Change

Help site follow-up for Use a floating action bar for bulk actions, which replaced the wide-layout bulk actions Selected dropdown on the Search pages with a floating bulk action bar at the bottom of the list.

Why the docs had to change: 20 step-by-step instructions across 13 articles told web users to click Selected at the top of the page. That control no longer exists on web, so following those steps now leads nowhere.

What changed in the product (verified against the live UI on web at 1600x900):

• Selecting rows on Expenses or Reports opens a bar floating over the bottom of the list, not a dropdown at the top.
• The bar shows up to three actions as buttons (two at medium widths). The rest move behind More, so which actions are buttons depends on the selection and window width.
• Actions with further choices, such as Export, open their own menu above the bar.
• A Select all selection shows a spinner in place of the count until the server total arrives.
• A selection with no available actions shows an explanation instead of buttons.
• The selection clears from the close button at the right end of the bar, or with Esc.
• Narrow layout (mobile, and browser windows narrow enough to use the mobile layout) is unchanged and keeps the Selected dropdown.
• The report view is unchanged and keeps its header dropdown.

Approach taken in the docs:

Because web and mobile now differ on one step only, that step names both platforms rather than duplicating each whole procedure:

3. Select **Delete**:
   - **Web:** In the bulk action bar at the bottom of the list, select **Delete**. If you don't see it, select **More**, then **Delete**.
   - **Mobile:** Tap **Selected**, then tap **Delete**.

The "if you don't see it, select More" hedge is deliberate: the bar decides at render time which actions get buttons, so no article can safely promise a given action is a button.

Getting-Started-with-the-Spend-Page.md gets one new ## How to use the bulk action bar on the Expenses and Reports pages section that explains the bar once, so the per-step instructions stay short.

Deliberately left alone:

• Instructions for selecting expenses inside a report (How-to-Merge-Expenses.md, How-to-Delete-Expenses.md) — the report view still uses Selected.
• The Report Tables section of Getting-Started-with-the-Spend-Page.md — same reason.
• Mobile-only sections, which still use Selected.
• Workspace settings tables (categories, tags, distance rates, per diem, members, personal expense rules) and the Expensify Card list — the PR only touched the Search pages, so those keep their Selected menus.

One incidental fix: the grouped-export steps in Search-and-Download-Expenses.md were missing the Export step between selecting rows and choosing Current view.

Files changed (13): View-and-Reconcile-Expensify-Card-Expenses.md, Adding-Attendees.md, Approve-Expenses.md, Create-and-Submit-Reports.md, Duplicate-a-Report.md, Edit-Expenses.md, Getting-Started-with-the-Spend-Page.md, How-to-Delete-Expenses.md, How-to-Duplicate-an-Expense.md, How-to-Export-Expenses.md, How-to-Export-Reports.md, How-to-Merge-Expenses.md, Search-and-Download-Expenses.md.

Applied docs/HELPSITE_NAMING_CONVENTIONS.md, docs/HELP_AUTHORING_GUIDELINES.md, and docs/TEMPLATE.md. npm run spell-changed passes on all 13 files (0 issues).

Fixed Issues

$ #98651
PROPOSAL:

Tests

// TODO: The human co-author must fill out the tests you ran before marking this PR as "ready for review"
// Please describe what tests you performed that validates your changed worked.

• Verify that no errors appear in the JS console

Offline tests

QA Steps

// TODO: The human co-author must fill out the QA tests you ran before marking this PR as "ready for review".
// Please describe what QA needs to do to validate your changes and what areas do they need to test for regressions.

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

---

@Krishna2323, please review the files changed and confirm they reflect the current behavior. Then post a new comment saying @MelvinBot mark this PR as ready for review.

[OSBotify]

A preview of your ExpensifyHelp changes have been deployed to https://efe2f1d9.helpdot.pages.dev ⚡️

Updated articles:

• articles/new-expensify/expensify-card/View-and-Reconcile-Expensify-Card-Expenses
• articles/new-expensify/reports-and-expenses/Adding-Attendees
• articles/new-expensify/reports-and-expenses/Approve-Expenses
• articles/new-expensify/reports-and-expenses/Create-and-Submit-Reports
• articles/new-expensify/reports-and-expenses/Duplicate-a-Report
• articles/new-expensify/reports-and-expenses/Edit-Expenses
• articles/new-expensify/reports-and-expenses/Getting-Started-with-the-Spend-Page
• articles/new-expensify/reports-and-expenses/How-to-Delete-Expenses
• articles/new-expensify/reports-and-expenses/How-to-Duplicate-an-Expense
• articles/new-expensify/reports-and-expenses/How-to-Export-Expenses
• articles/new-expensify/reports-and-expenses/How-to-Export-Reports
• articles/new-expensify/reports-and-expenses/How-to-Merge-Expenses
• articles/new-expensify/reports-and-expenses/Search-and-Download-Expenses