Fix - Owner can not be removed from workspace after transfer ownership

[FitseTLT]

Explanation of Change

When an admin transfers workspace ownership to themselves, the client only merges owner and ownerAccountID into the local policy on success. The backend also moves the payer, but the client never refreshes it, so getReimburserEmail keeps resolving to the former owner. The member details page hard-blocks removing the payer, so Remove from workspace dead-ends on an acknowledge-only modal until some unrelated refetch happens to correct the policy — which is why it starts working after a cache clear.

This refetches the policy when the transfer completes, so the client reads the payer the server already holds instead of re-deriving it. The transfer's successData also reassigns the payer optimistically to close the round-trip gap, but only when no bank account is connected and the outgoing owner is the resolved payer — with a bank account the backend keeps the former owner and rejects the removal, and a separately configured payer must not be touched. Separately, the removal prompt now checks isReimburser before isTechnicalContact, so a member who is both sees the copy for the condition that actually blocked them.

Fixed Issues

$ #96681
PROPOSAL: #96681 (comment)

Tests

1. As User A, create a workspace and invite User B as an Admin.
2. Sign in as User B, open Workspace → Members, and click User A to open their details page.
3. Click Transfer owner, then Got it on the success page.
4. Whenou land back on User A's member details page.
5. Click Remove from workspace.
6. Verify the modal has both Confirm and Cancel buttons — not a single acknowledge-only "Got it".
7. Confirm, and verify User A is removed from the workspace.
8. Repeat steps 1–3, then open Workspace → Workflows → Payments and verify the payer is now User B, not User A.
9. Also verify on User A's details page that the Role row is no longer disabled with the "role cannot be changed" hint.
10. Regression — bank account connected. As User A, connect a business bank account and set reimbursement so User A is the payer. Invite User B as an admin and transfer ownership to User B. As User B, open User A → Remove from workspace.
11. Verify the acknowledge-only modal still appears with the payer copy, and User A is not removed — the guard is correct here and the admin must reassign the payer first.

• Verify that no errors appear in the JS console

Offline tests

Same as tests

QA Steps

Same as tests

• Verify that no errors appear in the JS console

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I followed proper code patterns (see Reviewing the code)
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
• If new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

2026-08-28.23-13-08.mp4

[melvin-bot]

@Pujan92 Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

[codecov]

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines	Coverage Δ
src/libs/actions/Policy/Member.ts	79.05% <ø> (ø)
...s/workspace/members/WorkspaceMemberDetailsPage.tsx	73.29% <100.00%> (ø)
...orkspace/members/WorkspaceOwnerPaymentCardForm.tsx	0.00% <ø> (ø)
src/libs/actions/Policy/Policy.ts	71.70% <80.00%> (+0.28%)	⬆️
...ngs/Subscription/CardAuthenticationModal/index.tsx	0.00% <0.00%> (ø)
...members/DynamicWorkspaceOwnerChangeSuccessPage.tsx	0.00% <0.00%> (ø)
src/libs/PolicyUtils.ts	79.32% <50.00%> (-0.14%)	⬇️
... and 110 files with indirect coverage changes

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8d53e985a5

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[JmillsExpensify]

LGTM