Bank account - "Admins" title appears under the payer's name in Payments/ Payer

[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.11-1
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/folder/13176694/test-cases/41236763
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: MacBook Air 15.7.3 Chrome, iPhone 15 iOS 26.2
App Component: Workspace Settings

Action Performed:

1. Sign in to ND with a new gmail account, select "Manage my team's expenses"
2. Navigate to the Workflows - Payments, add a Regions 1111 bank account
3. In Payments tap "Payer" push row

Expected Result:

"Admins" title does not displayed under the payer's name

Actual Result:

"Admins" title appears under the payer's name in Payments/ Payer

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @trjExpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

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

[melvin-bot]

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

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

[OSBotify]

Investigation Summary

Classification: Frontend bug
Causing PR: #80321 - "Make EditReportFieldDropdown use new SelectionListWithSections" by @zfurtak (Medium confidence)
Related Issues: None identified

Recommendation: NEEDS INVESTIGATION

Further investigation is needed to confirm the root cause. PR #80321 refactored EditReportFieldDropdown to use the new SelectionListWithSections pattern, which may have introduced or exposed an issue with section title rendering that affects WorkspaceWorkflowsPayerPage.

Labels: Keeping DeployBlockerCash - this is a frontend issue in the App repository

Detailed Analysis

Evidence

The bug occurs in the Workspace Workflows Payer page (src/pages/workspace/workflows/WorkspaceWorkflowsPayerPage.tsx), which uses SelectionListWithSections to display two sections:

1. Authorized payer section (no title)
2. Admins section (title: "Admins")

The bug report states that "Admins" title appears under the payer name when it should not. This suggests an issue with how SelectionListWithSections renders section headers.

PR #80321 was merged on 2026-01-28 and refactored EditReportFieldDropdown to use the new SelectionListWithSections component pattern, changing from indexOffset to sectionIndex for section identification.

Verification

• The affected file is src/pages/workspace/workflows/WorkspaceWorkflowsPayerPage.tsx
• The component uses SelectionListWithSections which handles section header rendering via useFlattenedSections hook
• In useFlattenedSections.ts line 49, section headers are only created when section.title is truthy
• In BaseSelectionListWithSections.tsx lines 250-255, section headers render the title text

Root Cause

The issue may be related to:

1. Section title rendering logic in SelectionListWithSections not properly handling sections without titles
2. Recent refactoring of SelectionList components that changed how sections are processed
3. A regression introduced when migrating components to the new SelectionListWithSections pattern

Next Steps:

• Tag @zfurtak (PR author) for insights on SelectionListWithSections changes
• Test the Payer page on production vs staging to confirm the behavioral difference
• Review if other pages using SelectionListWithSections have similar issues
• Consider if the useFlattenedSections hook needs adjustment for section title handling

[OSBotify]

@zfurtak - Could you please review this issue? Your PR #80321 refactored EditReportFieldDropdown to use SelectionListWithSections, and there may be a related issue with section title rendering in WorkspaceWorkflowsPayerPage.

@jponikarchuk - Could you provide more details about the reproduction? Specifically:

1. Does the "Admins" text appear as a section header (separate row) or as part of the payer row itself?
2. Does it happen when there is only one admin who is also the payer, or in all cases?
3. Can you share the video/screenshot from the issue description?