Repository navigation
[Due for payment 2026-11-02] Members - Member's role can be changed to Approve-only when member has card on the workspace #104949
Description
If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.
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): applausetester+ssndjois2jd1@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Workspace Settings
Action Performed:
Precondition:
- User A creates a Control workspace and adds direct feed with cards to the workspace.
- User B has a default workspace.
- Perform the steps below as User A:
- Go to staging.new.expensify.com
- Go to workspace settings > Members.
- Invite User B as member.
- Go to workspace settings > Company card.
- Assign a card to User B.
- Go to workspace settings > Members.
- Change User B's role to Approve-only.
Expected Result:
User B's role cannot be changed to Approve-only because User B has a card on the workspace (admin cannot assign card to User B when User B's role is approve-only).
Actual Result:
User B's role can be changed to Approve-only when User B has a card on the workspace.
Workaround:
Unknown
Platforms:
- Android: App
- Android: mWeb Chrome
- iOS: App
- iOS: mWeb Safari
- iOS: mWeb Chrome
- Windows: Chrome
- MacOS: Chrome Safari
Screenshots/Videos
Bug7295604_1792861447806.19.mp4
Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7295604
Metadata
Metadata
Labels
Type
Projects
- Status
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/ed54e4d36f7275535f36f701b9aa3f4e4bd995247b5ccdec8e68ffcbefacd500
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 @madmax330 (
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
18 remaining items
melvin-bot commentedon Nov 1, 2026
Payment Summary
Resolving PRs:
Temporarily block approve-only role assignment #104952
Reviewer: @Pujan92 owed $175 via NewDot
Contributor: @ShridharGoel does not require payment (Contractor)
BugZero Checklist (@mallenexpensify)
melvin-bot commentedon Nov 2, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)melvin-bot commentedon Nov 3, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)mallenexpensify commentedon Nov 5, 2026
@Pujan92 this issue and/or PR mention a deploy blocker or a regression. Before the payment date, post one of the three options in step 20 of the C+ doc: it was a regression, it was not, or you did not review the offending PR. If you don't post, the default is to reduce payment.