[Due for payment 2026-01-27] Expense - Invited member cannot see Attendee field

[lanitochka17]

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.3-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #79050
Email or phone of affected tester (no customers): sdjsjdoisnjdoisjosdj22@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.1 / Chrome
App Component: Money Requests

Action Performed:

Preconditions:

• Rules are enabled.
• Enable Attendee tracking in Rules.

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Create two expenses.
4. Open the expense report.
5. Mention User B and send it to the report.
6. Click Invite to chat only.
7. As User B, open the report.

Expected Result:

User B can see Attendee field.

Actual Result:

Attendee field is hidden from User B.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7050309_1768498935765.6.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @brianlee-expensify

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #79050

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @brianlee-expensify (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.

[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: #79050 - "feat: add ability to require attendees based on category selection (rework)" by @ikevin127 (High confidence)
Related Issues: None identified

Recommendation: REVERT

PR #79050 introduced a regression where the Attendee field visibility is incorrectly tied to edit permissions. Users invited to "chat only" (not workspace members) cannot see the Attendee field because they lack edit permissions, even though they should be able to view it as read-only.

Labels: No changes needed - DeployBlockerCash is correctly applied for this Frontend bug.

📋 Detailed Analysis

Evidence

PR #79050 added the ability to require attendees based on category selection. The PR modified MoneyRequestView.tsx and added logic that ties the attendees field interactivity to the canEdit permission (line 1058: interactive={canEdit}).

Verification

The issue affects the attendees field in src/components/ReportActionItem/MoneyRequestView.tsx:

• Lines 1041-1065: The attendees field uses interactive={canEdit} and shouldShowRightIcon={canEdit}
• Line 324: canEdit is calculated based on whether the user is the expense creator, admin, or manager
• When a user is invited to "chat only", they are not a workspace member, so canEdit = false
• The MenuItemWithTopDescription component with interactive={false} makes the field appear disabled/hidden

Root Cause

The PR incorrectly assumed that attendee field visibility should be controlled by edit permissions. However, the expected behavior is:

• Workspace members with edit rights: Can edit the attendee field
• Invited chat-only users: Should see the attendee field as read-only, but cannot edit it

The regression is that interactive={canEdit} prevents chat-only users from seeing the field at all, when they should see it in a non-interactive (read-only) state.

Comparison

In MoneyRequestConfirmationListFooter.tsx (lines 737-758), the attendees field correctly uses isReadOnly instead of canEdit, which is the pattern that should have been followed in MoneyRequestView.tsx.