Domains - Domain members title has different font style as other sections

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.

---

Version Number: 9.4.54-1
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #98461
Email or phone of affected tester (no customers): applausetester+khcategory19@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Mac 26.5 / Chrome
App Component: Workspace Settings

Action Performed:

Precondition:

• Log in as domain admin (applausetester@applause.expensifail.com).

1. Go to staging.new.expensify.com
2. Go to Workspaces.
3. Go to Domains.
4. Open the domain where you are the admin.
5. Go to Domain members.

Expected Result:

Domain members title will have the same font style as other sections (eg, Domain admins, Groups).

Actual Result:

Domain members title has different font style as other sections (eg, Domain admins, Groups).

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7235105_1786896513133.8.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7235105

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022089248703677309909
• Upwork Job ID: 2089248703677309909
• Last Price Increase: 2026-08-17

Issue Owner

Current Issue Owner: @truph01

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/0895b68d69dc557bf51418048d5586a6b02b14ece5d42c90df2ae649dd2bc33e

https://platform.applause.com/services/links/v1/external/4e167b774a6d1d354738a640304687a6d3203d3a4b466bcb69e7ccbbe046de49

[MelvinBot]

Proposal

What is the root cause of that problem?

The Domain members page has two different header render paths, and only one of them uses the headline font:

• When the domain is not verified (the state in the screenshot — note the "Verify domain" CTA), the page renders its own header in DomainMembersPage.tsx:303. That HeaderWithBackButton is missing the shouldUseHeadlineHeader prop.
• Every sibling section header — Domain admins, Groups, SAML, and the verified Members view — passes shouldUseHeadlineHeader, which applies the textHeadlineH2 (New Kansas headline) font in HeaderWithBackButton/index.tsx:123.

Because the unverified Members header omits that prop, its title falls back to the default bold sans-serif header font, which is why it looks different from the other sections.

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

Add shouldUseHeadlineHeader to the HeaderWithBackButton in the unverified-domain branch of DomainMembersPage.tsx:303, so it matches the other section headers and the verified Members view.

Supporting evidence

• Screenshot URL is staging.new.expensify.com/domain/22320999/members and shows the "Verify domain" empty state → the unverified path at DomainMembersPage.tsx:294 is what renders.
• Sibling headers for comparison, all with shouldUseHeadlineHeader: DomainAdminsPage.tsx:148, DomainGroupsPage.tsx:117, and the verified Members header at BaseDomainMembersPage.tsx:87.
• Not a regression from the QA-source PR (\#98461): that PR only removed the decorative header illustrations. The diff hunk around this header (@@ -303,7 +303,6 @@) shows shouldUseHeadlineHeader was already absent before the PR, so this is a pre-existing inconsistency that the facelift QA surfaced.
• This is an App-only frontend fix (styling prop on an existing component).

---

Next Steps for Contributor+ team:
To accept: @MelvinBot implement [this](https://github.com/Expensify/App/issues/98748) to create a draft PR.
To refine: @MelvinBot <your feedback>
To reject: Explain why you are rejecting Melvin's proposal.

[melvin-bot]

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

[melvin-bot]

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

[truph01]

@linhvovan29546 Could I take over this one since it's a missing case from my original PR? #98461

cc @shawnborton

[shawnborton]

I will handle since this is related to my PR.

[shawnborton]

@MelvinBot can you please implement the fix for this?

[shawnborton]

And yes, going to reassign to @truph01 as a follow up.