[Due for payment 2026-03-19] Admin seeing competing RBR paths with broken company card connection

[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 (Reproduction blocked)
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: @joekaufmanexpensify
Slack conversation (hyperlinked to channel name): #Expensify Bugs

Action Performed:

1. Connect a direct feed and assign a card to the admin
2. Break the feed's connection

Expected Result:

Per this, the admin should see an RBR path directing them to the error on the company cards page. If they also have an assigned card, they should see an error on the card row on wallet, but not a full RBR path leading them to wallet. Only non-admin employees with an assigned card should see the RBR path leading them to the error on wallet.

Actual Result:

Workspace admin with assigned card on broken feed sees full RBR path leading them to the error on company cards AND on wallet.

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

Issue Owner

Current Issue Owner: @mallenexpensify

[melvin-bot]

Triggered auto assignment to @jliexpensify (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]

📣 @scerrato88! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:

1. Make sure you've read and understood the contributing guidelines.
2. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
3. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
4. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
   
   Format:

Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>

[chrispader]

@carlosmiceli i can tackle this. I should have a good idea where this needs to be fixed!

[carlosmiceli]

Hey Chris, no worries, I asked @hungvu193 to work on this one to tackle more issues in parallel so you and I can focus on our other existing open issues 🙏

[carlosmiceli]

Having said that, @hungvu193 please do ask Chris for pointers if it's hard to spot the solution 💪

[hungvu193]

@carlosmiceli i can tackle this. I should have a good idea where this needs to be fixed!

@chrispader Yeah I would love to hear your idea about fixing the RCA 🙏

[chrispader]

@carlosmiceli i can tackle this. I should have a good idea where this needs to be fixed!

@chrispader Yeah I would love to hear your idea about fixing the RCA 🙏

Alright, i'll let @hungvu193 handle this. @hungvu193 the issue should be located in the error states for workspace/account indicator in useNavigationTabBarIndicatorChecks.ts.

Currently, we show/hide the indicator based on whether the user is an admin of any workspace or not (isPolicyAdmin), but maybe we'll have to be specific with exact workspsace

[hungvu193]

Currently, we show/hide the indicator based on whether the user is an admin of any workspace or not (isPolicyAdmin), but maybe we'll have to be specific with exact workspsace

Oh I see. I remember I also concerned about it while reviewing the PR 😄. Let me take a look