You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Workspace - Workspace chat is not visible on member´s side when invited as "Approve-Only" #104944
Version Number: 9.5.20-0 Reproducible in staging?: Yes Reproducible in production?: N/A - new feature, doesn't exist in prod If this was caught during regression testing, add the test name, ID and link from BrowserStack:#102933 Email or phone of affected tester (no customers):ibellicotest+3292@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Motorola MotoG60 / Android 12 (Hybrid app) - Windows 11 / Chrome App Component: Workspace Settings
Action Performed:
Prerequisite: User A is owner of two "Control" workspaces. (Worksapce A and Workspace B)
Prerequisite 2: User B, already has a "Default" workspace.
Open the staging.new.expensify.com website.
Navigate to "Workspaces" > "Workspace A" > "Members"
Invite User B as "Member" of the workspace.
As User B, navigate to "Inbox"
Note that the new workspace chat is displayed.
As User A, click on User B on members list and edit role to "Approve-Only"
As User B, note that workspace chat remains visible.
As User A, navigate to "Workspace B" > "Members"
Invite User B with "Approve-Only" role.
As User B, note that new workspace chat is not visible on "Inbox"
Expected Result:
Workspace chat should be automatically visible on "Inbox" on member´s side, when invited with "Approve-Only" role.
Actual Result:
Workspace chat is not visible on member´s side when invited with "Approve-Only" role.
👋 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:
Identify the pull request that introduced this issue and revert it.
Why the chat is missing: The invite flow doesn't create a workspace chat for an Approve-only invitee. The chat isn't hidden in the Inbox; it never exists.
src/libs/actions/Policy/Member.ts:877-887 skips createPolicyExpenseChats when canRoleCreateExpenses(effectiveRole) is false. The code comment reads: "Roles that cannot create expenses don't get a workspace chat."
Why steps 6-7 differ from step 10: Changing an existing member to Approve-only keeps their existing chat. Inviting someone directly as Approve-only creates no chat. Both match the intended design for this role.
Investigation details
The PR was merged 2026-10-23 and is in the current staging deploy checklist.
The code comment came from an internal reviewer's suggestion during review, so the reviewers chose this behavior.
The PR's test and QA steps never say an Approve-only invitee gets a workspace chat.
The PR doesn't change Inbox/LHN filtering. It only hides create options inside the chat and removes the workspace from expense pickers.
If product decides Approve-only invitees should get a chat, that's a spec change for the App optimistic data and backend chat creation. It isn't a deploy-blocker fix.
No code-review rule is suggested because there's no defect.
Next Steps: The assigned engineer should confirm with flodnv (internal reviewer, currently OOO) before removing DeployBlockerCash. Reply with @MelvinBot <your feedback> to refine this analysis.
Activity
applause-bot commentedon Oct 26, 2026
While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/33c805dba94109c0d5c7cb448ce5f83a5387432ce90cb3a2d69b80a7d8a198aa
melvin-bot commentedon Oct 26, 2026
@flodnv recently merged #102933, but they are OOO right now, so I'll auto-assign someone else.
melvin-bot commentedon Oct 26, 2026
Triggered auto assignment to @lakchote (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Oct 26, 2026
👋 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:
melvin-bot commentedon Oct 26, 2026
@flodnv @Pujan92 you have been assigned to this deploy blocker because you reviewed the offending PR: #102933
melvin-bot commentedon Oct 26, 2026
@ShridharGoel you have been assigned to this deploy blocker because you authored the offending PR: #102933
melvin-bot commentedon Oct 26, 2026
💬 A slack conversation has been started in #expensify-open-source
MelvinBot commentedon Oct 26, 2026
Deploy Blocker Investigation
Verdict: Not a bug. Recommend removing
DeployBlockerCashand closing as expected behavior. Don't revert.Causing PR: [Payment due @Pujan92] Add approve-only workspace role (High confidence). It adds the Approve-only role and intentionally skips the workspace chat for roles that can't create expenses.
Why the chat is missing: The invite flow doesn't create a workspace chat for an Approve-only invitee. The chat isn't hidden in the Inbox; it never exists.
createPolicyExpenseChatswhencanRoleCreateExpenses(effectiveRole)is false. The code comment reads: "Roles that cannot create expenses don't get a workspace chat."APPROVE_ONLYread access to Overview and Members only, with noCREATE_EXPENSES.canRoleCreateExpensesreturns false for that role.Why steps 6-7 differ from step 10: Changing an existing member to Approve-only keeps their existing chat. Inviting someone directly as Approve-only creates no chat. Both match the intended design for this role.
Investigation details
Next Steps: The assigned engineer should confirm with
flodnv(internal reviewer, currently OOO) before removingDeployBlockerCash. Reply with@MelvinBot <your feedback>to refine this analysis.view run
ShridharGoel commentedon Oct 26, 2026
Expected