[Due for payment 2025-12-26] [$250] AccountSetting-Copilot access level not update when forward by shortcut

[mitarachim]

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: v9.2.60-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: N/A
Email or phone of affected tester (no customers): crowdtest.expensify+nhutadmin@gmail.com - crowdtest.expensify+nhutmem1@gmail.com
Issue reported by: Applause Internal Team
Device used: MacOS/Web
App Component: User Settings

Action Performed:

Pre-condition: Account was added Security > Copilot: Delegated access

1. Open Expensify
2. At Copilot: Delegated access , choose any user
3. Change Copilot type of that user to other option.
4. Fill in OTP > Saves
5. On History > Click Forward (Or Cmd + ] )

Expected Result:

Copilot: Delegated access level should be update to new value.

Actual Result:

Copilot: Delegated access level keep old value.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7007576_1763486840567.Screen_Recording_2025-11-19_at_00.15.49.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021993358037193822920
• Upwork Job ID: 1993358037193822920
• Last Price Increase: 2025-12-02

Issue Owner

Current Issue Owner: @bfitzexpensify

[melvin-bot]

Triggered auto assignment to @bfitzexpensify (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.

[mukhrr]

Proposal

Please re-state the problem that we are trying to solve in this issue.

When a user updates a Copilot's delegated access level and then navigates back/forward in browser history, the page displays the old access level instead of the updated one

What is the root cause of that problem?

We use route.params.currentRole to determine the selected role. Navigation parameters are static for a specific history entry, so when navigating history, route.params.currentRole retains the stale value from the initial navigation event.

App/src/pages/settings/Security/AddDelegate/UpdateDelegateRole/UpdateDelegateRolePage.tsx

Lines 42 to 50 in a7d994c

	const {currentRole, login} = route.params;
	const roleOptions = Object.values(CONST.DELEGATE_ROLE).map((role) => ({
	value: role,
	text: translate('delegate.role', {role}),
	keyForList: role,
	alternateText: translate('delegate.roleDescription', {role}),
	isSelected: role === currentRole,
	}));

What changes do you think we should make in order to solve the problem?

We should priorite user's account role

    const [account] = useOnyx(ONYXKEYS.ACCOUNT, {canBeMissing: true});

    const currentDelegate = account?.delegatedAccess?.delegates?.find((d) => d.email === login);
    const roleToDisplay = currentDelegate?.role ?? currentRole;

    const roleOptions = Object.values(CONST.DELEGATE_ROLE).map((role) => ({
        value: role,
        text: translate('delegate.role', {role}),
        keyForList: role,
        alternateText: translate('delegate.roleDescription', {role}),
        isSelected: role === roleToDisplay,
    }));

and need to update other necessary parts too

What alternative solutions did you explore? (Optional)

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021993358037193822920

[melvin-bot]

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