[No QA] Docs updates for E/A#91415 Add HR single connection limit FAQ

[MelvinBot]

Summary

• Adds a new FAQ entry to the New Expensify TriNet help article documenting that only one HR platform can be connected per workspace at a time
• Matches the new modal behavior added in [No QA] [HR Import] Show "You must disconnect first" modal  #91415 which shows "Cannot connect to multiple HR platforms" when a user tries to connect a second HR provider

Test plan

• Verify the updated TriNet article renders correctly on the help site
• Confirm FAQ content matches the actual product behavior introduced in [No QA] [HR Import] Show "You must disconnect first" modal  #91415

[OSBotify]

A preview of your ExpensifyHelp changes have been deployed to https://efae1133.helpdot.pages.dev ⚡️

Updated articles:

• articles/new-expensify/connections/TriNet

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR adds a single FAQ entry to the TriNet integration article, answering whether multiple HR platforms can be connected simultaneously. The new content is clear and actionable, with a few terminology and navigation path items worth verifying.

Scores Summary

• Readability: 9/10 - The answer is direct, gives a concrete example (Gusto), and provides actionable resolution steps. Easy to scan and understand.
• AI Readiness: 8/10 - The question-format heading is appropriate under the FAQ exemption and contains relevant keywords ("connect multiple HR platforms"). No metadata updates were needed for this addition.
• Style Compliance: 7/10 - Navigation path formatting is correct (bold), but two issues: (1) the path references Settings > Workspaces > [Workspace Name] > HR, while the existing article uses Settings > Workspaces > [Workspace Name] > Accounting with "HR Integrations" as a subsection -- this should be verified against the actual UI to ensure accuracy; (2) the terms "platform" and "provider" are used interchangeably within the same paragraph ("HR platform" appears three times, then "current provider" and "new one" at the end), which conflicts with the deterministic writing rule requiring consistent terminology.

Key Findings

• The navigation path in the new FAQ (> HR) differs from the path used earlier in the same article (> Accounting with "HR Integrations" subsection). One of these may be outdated or incorrect -- please verify against the current UI.
• Mixed terminology ("platform" vs. "provider") within a single answer reduces precision. Per the governance rule on deterministic writing: "Be consistent. Avoid stylistic variation."
• Positive: The FAQ heading is well-formed as a natural user question and the answer structure (limitation, example, resolution) is strong.

Recommendations

1. Verify the navigation path: Confirm whether the correct UI path is Settings > Workspaces > [Workspace Name] > HR or Settings > Workspaces > [Workspace Name] > Accounting > HR Integrations, and make it consistent with the rest of the article.
2. Standardize terminology: Pick either "platform" or "provider" and use it consistently throughout the answer. Since "HR platform" is used in the heading, consider replacing "current provider" with "current HR platform."

Pre-existing Issues (not scored)

The file has structural issues that predate this PR: multiple # headings (# Prerequisites, # Connect TriNet to Expensify) where only one is allowed per the authoring guidelines, and generic ## Step 1: / ## Step 2: headings that are explicitly forbidden. The internalScope metadata field is also missing. These should be addressed in a separate cleanup PR.

Files Reviewed

• docs/articles/new-expensify/connections/TriNet.md - New FAQ entry added; minor terminology and navigation path issues noted above.

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR adds a single FAQ entry to the TriNet help article, documenting that only one HR platform connection is supported per workspace at a time. The change is small, well-scoped, and addresses a real user scenario tied to new product behavior introduced in #91415.

Scores Summary

• Readability: 9/10 - The new FAQ answer is clear, concise, and actionable. It includes a concrete example (Gusto), explains the expected behavior (a prompt to disconnect), and provides a specific navigation path for resolving the situation. Sentence flow is natural and scannable.
• AI Readiness: 9/10 - The FAQ heading is a well-formed question ("Can I connect multiple HR platforms at the same time?") that matches realistic user search intent. It includes the key terms "HR platforms" and "connect" which support semantic retrieval. The heading follows the exemption rules for FAQ sections. Note: the existing file is missing the internalScope YAML field required by governance, but that is a pre-existing issue outside this diff's scope.
• Style Compliance: 9/10 - Navigation path is correctly bolded (**Settings > Workspaces > [Workspace Name] > HR**). UI terminology appears consistent with product conventions. The FAQ structure follows the expected pattern of direct answer followed by actionable guidance.

Key Findings

• The new FAQ entry is well-placed within the existing FAQ section, positioned logically before the employee notification question.
• The answer provides a complete user journey: what happens (prompt to disconnect), why (single connection limit), and how to resolve it (navigation to disconnect).
• All bold formatting for UI paths and elements follows the naming conventions.
• No prohibited language or vague navigation phrasing is used.

Recommendations

• No changes required for the proposed diff. The new FAQ entry is compliant with governance standards.
• (Out of scope for this PR, but worth noting for future work: the existing file has pre-existing governance gaps including missing internalScope in YAML frontmatter, multiple # headings beyond the title, and generic ## Step 1 / ## Step 2 headings that do not meet task-based heading requirements.)

Files Reviewed

• docs/articles/new-expensify/connections/TriNet.md - Single FAQ entry added. Compliant with governance standards. No issues found in the proposed changes.

[melvin-bot]

Concierge reviewer checklist:

• I have verified the accuracy of the article
  • The article is within a hub that makes sense, and the navigation is correct
  • All processes, screenshots, and examples align with current product behavior.
  • All links within the doc have been verified for correct destination and functionality.
• I have verified the readability of the article
  • The article's language is clear, concise, and free of jargon.
  • The grammar, spelling, and punctuation are correct.
  • The article contains at least one image, or that an image is not necessary
• I have verified the formatting of the article
  • The article has consistent formatting (headings, bullet points, etc.) with other HelpDot articles and that aligns with the HelpDot formatting standards.
  • The article has proper text spacing and breaks for readability.
• I have verified the article has the appropriate tone and style
  • The article's tone is professional, friendly, and suitable for the target audience.
  • The article's tone, terminology, and voice are consistent throughout.
• I have verified the overall quality of the article
  • The article is not missing any information, nor does it contain redundant information.
  • The article fully addresses user needs.
• I have verified that all requested improvements have been addressed

For more detailed instructions on completing this checklist, see How do I review a HelpDot PR as a Concierge Team member?

cc @strepanier03

[melvin-bot]

@strepanier03 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]

[strepanier03]

I reviewed the changes and the build. All looks good so I'm going to approve and merge.

[melvin-bot]

@strepanier03 looks like this was merged without a test passing. Please add a note explaining why this was done and remove the Emergency label if this is not an emergency.

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR adds a single new FAQ entry to the TriNet help article, documenting the one-HR-platform-per-workspace limitation. The change is small, well-scoped, and aligns with the product behavior introduced in #91415. The new content is clear, actionable, and follows governance conventions.

Scores Summary

• Readability: 9/10 - The new FAQ answer is concise, explains the constraint, describes what the user will see, and provides a clear remediation path with navigation instructions. Well structured.
• AI Readiness: 8/10 - The FAQ question uses a proper question format ("Can I...?"), which is compliant with heading rules. The question includes the key concept ("multiple HR platforms") making it retrievable. Minor deduction: the answer could benefit from including "TriNet" explicitly to strengthen retrieval for TriNet-specific searches (e.g., "Can I connect TriNet and another HR platform at the same time?").
• Style Compliance: 9/10 - Navigation path uses correct bold formatting (**Settings > Workspaces > [Workspace Name] > HR**). UI terminology appears consistent. Button/section names are bolded appropriately.

Key Findings

• The new FAQ entry is well-placed within the existing FAQ section and follows the question-then-answer pattern required by the template.
• The navigation path in the new FAQ references > HR while the existing connection steps reference > Accounting under HR Integrations. This may be intentional if they are genuinely different UI locations, but it is worth confirming the path matches the actual product UI exactly, per the Core UI Referencing Rules in the naming conventions.
• The answer provides a concrete example ("for example, Gusto") which aids user comprehension -- a good practice.
• Pre-existing issues in the file (missing internalScope in YAML frontmatter, non-task-based headings like # Prerequisites and ## Step 1/Step 2) are outside the scope of this diff and are not factored into scoring.

Recommendations

1. Verify the navigation path: Confirm that Settings > Workspaces > [Workspace Name] > HR matches the exact UI path in the product. The existing article uses > Accounting with an HR Integrations subsection, so ensure the disconnect path is accurate.
2. Consider strengthening retrieval: Optionally rephrase the question to include "TriNet" for better AI retrieval specificity, e.g., "Can I connect TriNet alongside another HR platform?"

Files Reviewed

• docs/articles/new-expensify/connections/TriNet.md - 4 lines added. New FAQ entry documenting single HR connection limit per workspace. Clean addition, no structural issues introduced.

Note: This review assessed only the proposed changes (the diff), not pre-existing content in the file.

[OSBotify]

🚀 Deployed to staging by https://github.com/strepanier03 in version: 9.3.90-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

Bundle Size Analysis (Sentry):

• Android
• iOS

[OSBotify]

🚀 Deployed to production by https://github.com/lakchote in version: 9.3.90-3 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅