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
[Due for payment 2026-08-08] [$250] Improve Copilot discoverability #92253
Copilot account switching is not sufficiently discoverable in the new product. In Classic, users could click the avatar in the top-right to get an account switcher dropdown. In the new product, this capability is buried in the navigation in a way that's non-obvious and takes more interactions than before.
Proposed Solution
Improve the Accounts page to make Copilot switching more immediately accessible by:
Replacing the Status icon with a Switch button for switching to different copilot accounts
Move Status to the Profile page
Add a tooltip for whenever someone goes to Accounts for the first time after being added as a copilot (or if we have a tooltip already, we'd update it).
Since we're adding the switch button, then we no longer need to make the email + profile photo clickable.
Move the Copilot Access tooltip to the Switch button instead of leaving it in its current location
Please re-state the problem that we are trying to solve in this issue.
The Copilot account-switching feature on the Accounts page is not discoverable: the only way to switch accounts is an implicit tap on the avatar/email with no labeled CTA, the Status icon occupies the right-side action slot where a "Switch" button should live, and there is no first-time tooltip guiding newly-added copilots to the feature.
What is the root cause of that problem?
Honest assessment: The investigation context contains no source code windows, no symbol definitions, and no cross-references. The root cause is therefore a UX affordance gap whose exact file locations must be stated as best-effort based on the Expensify/App codebase conventions and the issue's own screenshots and description. No fabricated line numbers will be cited.
The problem has four concrete components:
No explicit Switch button — the delegate account row uses an implicit onPress on the whole row (avatar + email tap) rather than a labeled Button component in the right-side slot.
Status icon in wrong location — the right-side accessory of each delegate row renders a Status component that should instead live on the Profile page.
No first-time discovery tooltip — when a user is added as a copilot for the first time, there is no tooltip drawing attention to the switching action.
"Copilot Access" tooltip is on the row rather than the Switch button — after the Switch button is added, the tooltip should attach to it.
The most likely files involved, based on the issue description, the design screenshots, and standard Expensify codebase layout:
src/pages/settings/Profile/ProfilePage.tsx — needs a Status menu item added
The delegate/accounts list component (rendered under the Accounts section of Settings) — needs the Status right-accessory replaced with a SwitchButton, row tap-through removed, and a first-time tooltip added
src/languages/en.ts and src/languages/es.ts — new translation keys
An Onyx key / NVP for tracking "has seen copilot switch tooltip" — needs to be defined and read/written
Because no source code was surfaced in the investigation context, the proposal below is written as a precise implementation guide using only real Expensify component and pattern conventions, clearly flagging every location that a contributor must verify before submitting a PR.
What changes do you think we should make in order to solve the problem?
Step 0 — Locate the real delegate list file (contributor must verify)
Search the codebase for the component that renders the list of delegated accounts on the Accounts page. Likely candidates (contributor must grep to confirm):
The result will be the file for File 1 below. Common candidates based on Expensify conventions:
src/pages/settings/Profile/ProfilePage.tsx (if accounts are listed inline)
A dedicated component imported by ProfilePage or a Settings navigator screen
File 1 — Delegate account list component (path to be confirmed by grep above)
Concept of change: Replace the Status right-accessory with a SwitchButton. Remove onPress from the row itself. Wrap the button in a EducationalTooltip (or Tooltip) that is visible only on the user's first visit after being added as a copilot.
// BEFORE (representative pattern — exact props must be verified against real file)<MenuItemtitle={account.displayName}description={account.email}icon={{uri: account.avatar}}rightComponent={<Status/>}onPress={()=>switchToDelegateAccount(account.email)}/>// AFTERimportButtonfrom'@components/Button';importEducationalTooltipfrom'@components/Tooltip/EducationalTooltip';// OR if EducationalTooltip does not exist, use the pattern from// src/components/Tooltip/index.tsx with
⚠️@aswin-s Your proposal is a duplicate of an already existing proposal and has been automatically withdrawn to prevent spam. Please review the existing proposals before submitting a new one.
[Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to the comment on the PR: NA. This is a new feature.
Link to the comment on the Issue: NA.
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: NA
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
@mallenexpensify Checklist done. We went down a rabbit hole to fix edge cases and managed to land this new feature with a second try. It'll be great if you could consider waiving the penalty for payment. Thanks!
Activity
melvin-bot commentedon Jun 1, 2026
Triggered auto assignment to Design team member for new feature review - @dannymcclain (
NewFeature)melvin-bot commentedon Jun 1, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @eh2077 (
External)[-]Improve Copilot discoverability[/-][+][$250] Improve Copilot discoverability[/+]melvin-bot commentedon Jun 1, 2026
Job added to Upwork: https://www.upwork.com/jobs/~022061475500472545363
ReaperOAK commentedon Jun 1, 2026
Proposal
Please re-state the problem that we are trying to solve in this issue.
The Copilot account-switching feature on the Accounts page is not discoverable: the only way to switch accounts is an implicit tap on the avatar/email with no labeled CTA, the
Statusicon occupies the right-side action slot where a "Switch" button should live, and there is no first-time tooltip guiding newly-added copilots to the feature.What is the root cause of that problem?
Honest assessment: The investigation context contains no source code windows, no symbol definitions, and no cross-references. The root cause is therefore a UX affordance gap whose exact file locations must be stated as best-effort based on the Expensify/App codebase conventions and the issue's own screenshots and description. No fabricated line numbers will be cited.
The problem has four concrete components:
onPresson the whole row (avatar + email tap) rather than a labeledButtoncomponent in the right-side slot.Statusicon in wrong location — the right-side accessory of each delegate row renders a Status component that should instead live on the Profile page.The most likely files involved, based on the issue description, the design screenshots, and standard Expensify codebase layout:
src/pages/settings/Profile/ProfilePage.tsx— needs aStatusmenu item addedStatusright-accessory replaced with aSwitchButton, row tap-through removed, and a first-time tooltip addedsrc/languages/en.tsandsrc/languages/es.ts— new translation keysBecause no source code was surfaced in the investigation context, the proposal below is written as a precise implementation guide using only real Expensify component and pattern conventions, clearly flagging every location that a contributor must verify before submitting a PR.
What changes do you think we should make in order to solve the problem?
Step 0 — Locate the real delegate list file (contributor must verify)
Search the codebase for the component that renders the list of delegated accounts on the Accounts page. Likely candidates (contributor must
grepto confirm):The result will be the file for File 1 below. Common candidates based on Expensify conventions:
src/pages/settings/Profile/ProfilePage.tsx(if accounts are listed inline)ProfilePageor a Settings navigator screenFile 1 — Delegate account list component (path to be confirmed by
grepabove)Concept of change: Replace the
Statusright-accessory with aSwitchButton. RemoveonPressfrom the row itself. Wrap the button in aEducationalTooltip(orTooltip) that is visible only on the user's first visit after being added as a copilot.aswin-s commentedon Jun 1, 2026
🚫 Duplicated proposal withdrawn by 🤖 ProposalPolice.
github-actions commentedon Jun 1, 2026
95 remaining items
eh2077 commentedon Aug 7, 2026
BugZero Checklist:
[Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to the comment on the PR: NA. This is a new feature.
Link to the comment on the Issue: NA.
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: NA
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
We don't need regression test here.
eh2077 commentedon Aug 7, 2026
@mallenexpensify Checklist done. We went down a rabbit hole to fix edge cases and managed to land this new feature with a second try. It'll be great if you could consider waiving the penalty for payment. Thanks!
mallenexpensify commentedon Aug 11, 2026
@inimaga for this issue, @eh2077 is requesting to not have the amount reduced, can you chime in? It def seems like a doozy of an issue. Thx
inimaga commentedon Aug 11, 2026
@mallenexpensify Yeah, I agree and think we should keep the current amount.
mallenexpensify commentedon Aug 12, 2026
Payment Summary
Contributor: @wildan-m paid $250 via Upwork
Contributor+: @eh2077 due $250 via NewDot
laurenreidexpensify commentedon Sep 4, 2026
$250 approved @eh2077 New Expensify