Skip to content

[Due for payment 2026-08-08] [$250] Improve Copilot discoverability #92253

Closed

Description

@flaviadefaria

Problem

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
Image Image Image

References

Upwork Automation - Do Not Edit
Issue OwnerCurrent Issue Owner: @mallenexpensify

Activity

  1. melvin-bot commented on Jun 1, 2026

    @melvin-bot

    Triggered auto assignment to Design team member for new feature review - @dannymcclain (NewFeature)

  2. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Jun 1, 2026
  3. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jun 1, 2026
  4. melvin-bot commented on Jun 1, 2026

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @eh2077 (External)

  5. changed the title [-]Improve Copilot discoverability[/-] [+][$250] Improve Copilot discoverability[/+] on Jun 1, 2026
  6. melvin-bot commented on Jun 1, 2026

    @melvin-bot
  7. ReaperOAK commented on Jun 1, 2026

    @ReaperOAK
    Contributor

    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 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:

    1. 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.
    2. 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.
    3. 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.
    4. "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 Switch Button, 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):

    grep -r "delegateAccount\|DelegateList\|switchAccount\|copilotAccount" src/pages/settings --include="*.tsx" -l
    grep -r "Status.*rightComponent\|rightComponent.*Status" src/pages/settings --include="*.tsx" -l
    

    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 Switch Button. 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)
    <MenuItem
        title={account.displayName}
        description={account.email}
        icon={{uri: account.avatar}}
        rightComponent={<Status />}
        onPress={() => switchToDelegateAccount(account.email)}
    />
    
    // AFTER
    import Button from '@components/Button';
    import EducationalTooltip from '@components/Tooltip/EducationalTooltip';
    // OR if EducationalTooltip does not exist, use the pattern from
    // src/components/Tooltip/index.tsx with
  8. aswin-s commented on Jun 1, 2026

    @aswin-s
    Contributor

    🚫 Duplicated proposal withdrawn by 🤖 ProposalPolice.

  9. github-actions commented on Jun 1, 2026

    @github-actions
    Contributor

    ⚠️ @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.

  10. 95 remaining items

  11. eh2077 commented on Aug 7, 2026

    @eh2077
    Contributor

    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.

  12. eh2077 commented on Aug 7, 2026

    @eh2077
    Contributor

    @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!

  13. added and removed on Aug 10, 2026
  14. added and removed on Aug 10, 2026
  15. mallenexpensify commented on Aug 11, 2026

    @mallenexpensify
    Contributor

    @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

  16. inimaga commented on Aug 11, 2026

    @inimaga
    Contributor

    @mallenexpensify Yeah, I agree and think we should keep the current amount.

  17. mallenexpensify commented on Aug 12, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor: @wildan-m paid $250 via Upwork
    Contributor+: @eh2077 due $250 via NewDot

  18. laurenreidexpensify commented on Sep 4, 2026

    @laurenreidexpensify
    Contributor

    $250 approved @eh2077 New Expensify

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionDailyKSv2ExternalAdded to denote the issue can be worked on by a contributorNewFeatureSomething to build that is a new item.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions