Skip to content

[$250] Assigning Expensify Card in One Workspace Automatically Adds User to Another Workspace #91014

@m-natarajan

Description

@m-natarajan

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:
Reproducible in staging?: Needs reproduction (Unable to reproduce)
Reproducible in production?: Needs reproduction
If this was caught during regression testing, add the test name, ID and link from BrowserStack:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @CCKroetsch
Slack conversation (hyperlinked to channel name): #Expensify Bugs

Action Performed:

  1. Have: Workspace A and Workspace B
  2. As admin, assign an Expensify card to User A in Workspace A
  3. Observe workspace memberships for User A

Expected Result:

User A should:
Only be added to and assigned a card in Workspace A

Actual Result:

User A is:
Automatically added to Workspace B as well

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

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

Screenshots/Videos

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~022056460364304087373
  • Upwork Job ID: 2056460364304087373
  • Last Price Increase: 2026-06-08

Metadata

Metadata

Assignees

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributors

Type

No type
No fields configured for issues without a type.

Projects

Status
Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions