[$250] Update Approved! Partner Help Page Support Options

[MitchExpensify]

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: NA - New Feature
Reproducible in staging?: NA - New Feature
Reproducible in production?: NA - New Feature
If this was caught during regression testing, add the test name, ID and link from BrowserStack: NA - New Feature
Email or phone of affected tester (no customers): NA - New Feature
Logs: https://stackoverflow.com/c/expensify/questions/4856 NA - New Feature
Expensify/Expensify Issue URL: https://github.com/Expensify/Expensify/issues/634684
Issue reported by: mitch@expensify.com
Slack conversation (hyperlinked to channel name): https://expensify.slack.com/archives/C05P8G4A1SP/p1778603383299499

Action Performed:

1. Open https://new.expensify.com/settings/help as an APPROVED ACCOUNTANT account

Expected Result:

Figma file: https://www.figma.com/design/nr4KuP6OBh1CLafBVvhOCK/Relationship-manager?node-id=153-24179&t=i2Uk0GRDhJ0t6KQy-11

BANNER
Expensify
Approved!

---

SECTION HEADER
"Meet your Approved! partner team"

SECTION DESCRIPTION
"A dedicated team focused on helping your firm grow, onboard clients faster, and get expert support whenever you need it."

---

NOTE: The names below are placeholder names only — replace with real data at runtime.

ROLE LABEL: "Partner Manager"
NAME: [Partner Manager Name]
DESCRIPTION: "Maximize your partnership and drive referrals"

ROLE LABEL: "Account Executive"
NAME: [Account Executive Name]
DESCRIPTION: "Get clients setup successfully"
ROW ACTION: Chevron right — navigates to detail/chat view

ROLE LABEL: "Account Manager"
NAME: [Account Manager Name]
DESCRIPTION: "Ask questions and get client support"

---

SECTION LABEL
"More resources"

ITEM: "Concierge"
DESCRIPTION: "Your personal AI agent"

ITEM: "ExpensifyHelp site"
DESCRIPTION: "Articles, tutorials, and more"

Actual Result:

Current web page is shown

Workaround:

NA

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022055129366931252505
• Upwork Job ID: 2055129366931252505
• Last Price Increase: 2026-05-15

Issue Owner

Current Issue Owner: @amyevans

[melvin-bot]

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

[mukhrr]

@dubielzyk-expensify can you pls give access to figma or share slides here?! mshakhriyorov8@gmail.com thanks!

[MelvinBot]

Proposal

What is the root cause of that problem?

The HelpPage currently renders a single flat list of support contacts (Concierge, Account Manager, Partner Manager, Guide, Help Site). It has no awareness of the isApprovedAccountant flag on the Account Onyx object, so it cannot show a differentiated experience for Approved Accountant users — no banner, no dedicated "partner team" section, and no "Account Executive" role.

The existing support contacts (Account Manager, Partner Manager, Guide) are gated on isPaidPolicyAdmin rather than isApprovedAccountant, so Approved Accountants who are not paid policy admins won't see their assigned contacts at all.

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

When account?.isApprovedAccountant is true, render an alternate layout in HelpPage.tsx:

1. Banner — Add an ExpensifyApprovedLogo banner at the top of the page (similar pattern to the subscription page badge).

2. "Meet your Approved! partner team" section — A new Section with a title/subtitle showing the three partner contacts as menu items:

   • Partner Manager — already available via account.partnerManagerAccountID
   • Account Executive — new field needed on Account type (accountExecutiveAccountID). The backend GetAssignedSupportData API must be updated to return this. Add the field to Account.ts.
   • Account Manager — already available via account.accountManagerAccountID

   Each item opens a DM via navigateToAndOpenReportWithAccountIDs. Gate visibility on isApprovedAccountant (not isPaidPolicyAdmin).

3. "More resources" section — A second Section with:

   • Concierge (existing item, with description "Your personal AI agent")
   • ExpensifyHelp site (existing item, with description "Articles, tutorials, and more")

4. Translations — Add new strings in en.ts / es.ts for the banner text, section headers, section descriptions, and role descriptions per the Figma spec.

Key implementation notes

• The isApprovedAccountant flag is already populated by the backend and typed in Account.ts:156.
• The GetAssignedSupportData API (Help.ts:4-6) already runs on page mount and populates partner contacts — it just needs to also return the Account Executive data.
• The ExpensifyApprovedLogo illustration is already used on the subscription page and can be reused.
• Non-approved-accountant users should continue to see the current Help page unchanged.
• Backend dependency: A backend change is required to return accountExecutiveAccountID from GetAssignedSupportData. This should be tracked in a separate Expensify/Expensify issue.

---

Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, @MelvinBot <your feedback> to refine this analysis, or explain why you are rejecting Melvin's proposal.

[KJ21-ENG]

🚨 Edited by proposal-police: This proposal was edited at 2026-05-15 03:37:09 UTC.

Proposal

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

Approved Accountant users who open /settings/help still see the generic Help page. They should instead see the Approved! partner support page with the Approved! banner, the dedicated partner team section, the three assigned support contacts, and the More resources section.

What is the root cause of that problem?

HelpPage always renders the generic help section. The page does call GetAssignedSupportData on mount, and it already reads assigned support data from account.accountManagerAccountID, account.partnerManagerAccountID, and account.guideDetails.email, but that data is only appended to the generic menu when useIsPaidPolicyAdmin() returns true.

The account model already exposes isApprovedAccountant, but HelpPage never branches on it. So an Approved Accountant account has the flag needed for the new experience, but the UI path only knows how to render the old "Got questions?" layout, old role copy, and old single-list resource structure.

The expected screenshot also shows Account Executive as a distinct visible role. The current frontend type has Account Manager, Partner Manager, and Guide support fields, but no explicitly typed Account Executive field, so the implementation needs to either use the existing Guide support payload only if that is the backend-owned Account Executive contact, or add a typed Account Executive field returned by GetAssignedSupportData.

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

Add an Approved Accountant variant to src/pages/settings/HelpPage/HelpPage.tsx that renders when account?.isApprovedAccountant is true.

Concretely:

• Keep calling openHelpPage() so GetAssignedSupportData populates the support contacts.
• Build separate partner-team rows from runtime support data:
  • Partner Manager from partnerManagerAccountID
  • Account Executive from the Account Executive support payload; if the backend currently represents this as guideDetails.email, reuse that field with the new role label/copy, otherwise add accountExecutiveAccountID / accountExecutiveEmail to the Account Onyx type and return it from GetAssignedSupportData
  • Account Manager from accountManagerAccountID
• Gate these partner-team rows on account?.isApprovedAccountant, not isPaidPolicyAdmin, since the requested experience is for Approved Accountant accounts.
• Use the requested role labels, names, and descriptions in new translation keys. Rows with a contact should navigate with navigateToAndOpenReportWithAccountIDs the same way the existing support rows do.
• Replace the generic section copy for Approved Accountant accounts with the requested "Meet your Approved! partner team" heading and description.
• Add a top Approved! banner using the existing themed ExpensifyApprovedLogo asset already used in subscription settings, plus the "Expensify / Approved!" copy from the design.
• Split "Concierge" and "ExpensifyHelp site" into a "More resources" section. Concierge should continue using openConciergeAnywhere, and ExpensifyHelp should continue opening CONST.NEWHELP_URL with the new "Articles, tutorials, and more" description.

This should be scoped to Approved Accountant accounts only. Non-Approved users should continue to see the existing generic Help page behavior.

What alternative solutions did you explore? (Optional)

We could replace the existing Help page for every user with a more generic support-team abstraction, but that increases risk for non-Approved users and changes unrelated behavior. A small isApprovedAccountant branch is the lower-risk path because the requested UI is specific to Approved! partner accounts and the existing generic page is still valid for everyone else.

[mukhrr]

Proposal

What is the root cause of that problem?

HelpPage.tsx renders a single layout for every user. There's no branch that detects an Approved! partner (account.isApprovedAccountant) and swaps in the partner-specific design — banner, "Meet your Approved! partner team" section, or the split between team contacts and "More resources." The existing role rows are also gated on isPaidPolicyAdmin, not on isApprovedAccountant, so an approved accountant who isn't a paid policy admin would see none of them.

The conditional rendering of the role rows lives here:

App/src/pages/settings/HelpPage/HelpPage.tsx

Lines 60 to 104 in 1b89b63

	title: accountManagerDetails.displayName,
	description: translate('initialSettingsPage.helpPage.accountManagerDescription'),
	icon: accountManagerDetails.avatar,
	iconType: CONST.ICON_TYPE_AVATAR,
	onPress: () => navigateToAndOpenReportWithAccountIDs([accountManagerDetails.accountID], currentUserAccountID, introSelected, isSelfTourViewed, betas),
	shouldShowRightIcon: true,
	wrapperStyle: [styles.sectionMenuItemTopDescription],
	sentryLabel: CONST.SENTRY_LABEL.SETTINGS_HELP.ACCOUNT_MANAGER,
	},
	]
	: []),
	...(partnerManagerDetails && isPaidPolicyAdmin
	? [
	{
	key: partnerManagerDetails.login,
	title: partnerManagerDetails.displayName,
	description: translate('initialSettingsPage.helpPage.partnerManagerDescription'),
	icon: partnerManagerDetails.avatar,
	iconType: CONST.ICON_TYPE_AVATAR,
	onPress: () => navigateToAndOpenReportWithAccountIDs([partnerManagerDetails.accountID], currentUserAccountID, introSelected, isSelfTourViewed, betas),
	shouldShowRightIcon: true,
	wrapperStyle: [styles.sectionMenuItemTopDescription],
	sentryLabel: CONST.SENTRY_LABEL.SETTINGS_HELP.PARTNER_MANAGER,
	},
	]
	: []),
	...(guideDetails && isPaidPolicyAdmin
	? [
	{
	key: guideDetails.login,
	title: guideDetails.displayName,
	description: translate('initialSettingsPage.helpPage.guideDescription'),
	icon: guideDetails.avatar,
	iconType: CONST.ICON_TYPE_AVATAR,
	onPress: () => navigateToAndOpenReportWithAccountIDs([guideDetails.accountID], currentUserAccountID, introSelected, isSelfTourViewed, betas),
	shouldShowRightIcon: true,
	wrapperStyle: [styles.sectionMenuItemTopDescription],
	sentryLabel: CONST.SENTRY_LABEL.SETTINGS_HELP.GUIDE,
	},
	]
	: []),
	{
	key: 'initialSettingsPage.helpPage.helpSite',
	title: translate('initialSettingsPage.helpPage.helpSite'),
	icon: illustrations.Chalkboard,

Additionally, the data model in src/types/onyx/Account.ts already carries partnerManagerAccountID, accountManagerAccountID, and isApprovedAccountant, but there's no field for the new Account Executive role required by the design:

App/src/types/onyx/Account.ts

Lines 107 to 156 in 1b89b63

	/** The Account ID of the account manager */
	accountManagerAccountID?: string;
	/** The Report ID of the account manager */
	accountManagerReportID?: string;
	/** The account ID of the partner manager */
	partnerManagerAccountID?: number;
	/** The email of the partner manager */
	partnerManagerEmail?: string;
	/** The message to be displayed when code requested */
	message?: string;
	/** Form that is being loaded */
	loadingForm?: ValueOf<typeof CONST.FORMS>;
	/** Whether the user forgot their password */
	forgotPassword?: boolean;
	/** Whether the account exists */
	accountExists?: boolean;
	/** Is the account / domain under domain control? */
	domainControlled?: boolean;
	/** Whether the validation code has expired */
	validateCodeExpired?: boolean;
	/** Whether a sign is loading */
	isLoading?: boolean;
	/** Authentication failure errors */
	errors?: OnyxCommon.Errors | null;
	/** Errors related to specific account fields */
	errorFields?: OnyxCommon.ErrorFields;
	/** Authentication success message */
	success?: string;
	/** Whether the two factor authentication codes were copied */
	codesAreCopied?: boolean;
	/** Referral banners that the user dismissed */
	dismissedReferralBanners?: DismissedReferralBanners;
	/** Indicates whether the user is an approved accountant */
	isApprovedAccountant?: boolean;

And the help page copy lacks every new string referenced in the Figma (banner title, team section title/subtitle, role labels, Account Executive description, "More resources" section header):

App/src/languages/en.ts

Lines 2166 to 2175 in 1b89b63

	},
	security: 'Security',
	signOut: 'Sign out',
	restoreStashed: 'Restore stashed login',
	signOutConfirmationText: "You'll lose any offline changes if you sign out.",
	versionLetter: 'v',
	readTheTermsAndPrivacy: `Read the <a href="${CONST.OLD_DOT_PUBLIC_URLS.TERMS_URL}">Terms of Service</a> and <a href="${CONST.OLD_DOT_PUBLIC_URLS.PRIVACY_URL}">Privacy</a>.`,
	help: 'Help',
	helpPage: {
	title: 'Got questions?',

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

1. Add the new Approved! partner fields to the Account Onyx type so the Account Executive can flow through to the FE, alongside the existing partner/account manager IDs:

     /** The account ID of the partner manager */
     partnerManagerAccountID?: number;

     /** The email of the partner manager */
     partnerManagerEmail?: string;

+    /** The account ID of the account executive (Approved! partner program) */
+    accountExecutiveAccountID?: number;
+
+    /** The email of the account executive (Approved! partner program) */
+    accountExecutiveEmail?: string;

The BE should populate these on the OpenApp/ReconnectApp response for accounts where isApprovedAccountant === true.

2. Branch the help page on isApprovedAccountant and render the Approved! layout. I'd extract the partner layout into a sibling ApprovedPartnerHelpPage.tsx so HelpPage.tsx stays small, and switch at the top:

 function HelpPage() {
     ...
     const [account] = useOnyx(ONYXKEYS.ACCOUNT);
+    if (account?.isApprovedAccountant) {
+        return <ApprovedPartnerHelpPage />;
+    }
     ...
 }

ApprovedPartnerHelpPage reuses the existing ScreenWrapper + HeaderWithBackButton shell, but:

• Renders the Approved! banner illustration at the top (new asset from the Figma, added under assets/images/ and exported through useMemoizedLazyIllustrations).
• Renders a Section titled initialSettingsPage.approvedPartnerHelpPage.teamTitle with subtitle …teamDescription, containing three MenuItems built from partnerManagerAccountID, accountExecutiveAccountID, and accountManagerAccountID (same navigateToAndOpenReportWithAccountIDs handler that exists today, only the Account Executive row needs the chevron / shouldShowRightIcon, per the design).
• Renders a second Section titled initialSettingsPage.approvedPartnerHelpPage.moreResourcesTitle containing the existing Concierge row and the ExpensifyHelp site row.
• Gates each role row only on whether the corresponding *AccountID is present — drop the isPaidPolicyAdmin check inside this branch, since Approved! partners always have a partner team regardless of paid policy admin status.

3. Add new copy under initialSettingsPage.approvedPartnerHelpPage in src/languages/en.ts (other languages added later, per the usual incremental flow):

• bannerTitle: 'Approved!'
• teamTitle: 'Meet your Approved! partner team'
• teamDescription: 'A dedicated team focused on helping your firm grow, onboard clients faster, and get expert support whenever you need it.'
• partnerManagerRole: 'Partner Manager' / partnerManagerDescription: 'Maximize your partnership and drive referrals'
• accountExecutiveRole: 'Account Executive' / accountExecutiveDescription: 'Get clients setup successfully'
• accountManagerRole: 'Account Manager' / accountManagerDescription: 'Ask questions and get client support'
• moreResourcesTitle: 'More resources'

I'd also add SETTINGS_HELP.ACCOUNT_EXECUTIVE to CONST.SENTRY_LABEL to mirror the other role rows.

What alternative solutions did you explore? (Optional)

N/A

Result: (Pls, note main banner image will be replaced later in PR)

[melvin-bot]

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

[melvin-bot]

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