[No QA] Rename Zenefits to TriNet

[stephanieelliott]

See: https://github.com/Expensify/Expensify/issues/598902#issuecomment-3882874170

[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 @CortneyOfstad

[melvin-bot]

@arosiclair @CortneyOfstad One of you needs to 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]

NOTE: It looks like docs/redirects.csv was modified in this PR. Please see this SO for special instructions on how to review changes to that file.

[github-actions]

Readability violation: Missing breadcrumb path after the H1 heading. Add the navigation path for better user orientation.

This section should include where users can find prerequisite information or settings.

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR renames the Zenefits integration to TriNet across documentation files. The changes are straightforward and consist primarily of a find-and-replace operation. The documentation maintains consistent quality throughout, with clear structure, proper formatting, and appropriate content for both technical accuracy and user readability.

Scores Summary

• Readability: 9/10 - The documentation is well-written with clear, jargon-free language at an appropriate reading level. Logical flow is excellent with proper use of bullets, numbered steps, and formatting elements. Minor deduction for the title field still using ".md" extension in the filename.
• AI Readiness: 8/10 - Good metadata structure with descriptive headings and clear context. The keywords field appropriately includes both "TriNet" and "Zenefits" for searchability. However, the title field contains "TriNet-Integration.md" (including file extension) which should be "TriNet Integration" for proper display. The file path itself (Zenefits.md) was not updated to match the new naming, which could cause confusion.
• Style Compliance: 9/10 - Excellent adherence to Expensify style guidelines with correct terminology (workspace, member, admin), proper button labels, and consistent markdown formatting. FAQ structure follows standards perfectly. The integration maintains proper voice and tone throughout.

Key Findings

Positive Aspects:

• Comprehensive coverage: All instances of "Zenefits" were successfully replaced with "TriNet" throughout the content
• Consistency maintained: The rename was applied uniformly across feature descriptions, steps, FAQs, and prerequisites
• Proper redirect added: The redirects.csv file correctly maps the old Zenefits URL to the new TriNet URL, ensuring backward compatibility
• Strong documentation structure: Clear prerequisites, step-by-step instructions, and helpful FAQ section
• Good metadata practices: Keywords include both old and new names for search continuity

Issues Identified:

1. File path mismatch (Critical): The file is still named Zenefits.md but should be renamed to TriNet.md to match the content
2. Title field format (Minor): The title field contains "TriNet-Integration.md" - it should be "TriNet Integration" (human-readable format without file extension)
3. Metadata consistency: The description and keywords correctly reference TriNet, but the physical filename does not

Recommendations

Critical Actions Required:

1. Rename the file: docs/articles/expensify-classic/connections/Zenefits.md should be renamed to docs/articles/expensify-classic/connections/TriNet.md
2. Update redirects: After renaming the file, ensure the redirect in redirects.csv points to the correct new file path
3. Fix title metadata: Change title: TriNet-Integration.md to title: TriNet Integration

Optional Improvements:

1. Consider adding a note at the top of the document mentioning "Formerly known as Zenefits" for users who might be familiar with the old name
2. Verify that any internal links or cross-references in other documentation files that point to this page are updated

Files Reviewed

• docs/articles/expensify-classic/connections/Zenefits.md: Comprehensive rename from Zenefits to TriNet; well-structured content; needs file rename and title fix
• docs/articles/new-expensify/billing-and-subscriptions/Plan-types-and-pricing.md: Single instance correctly updated in the HR & payroll sync row; no issues
• docs/redirects.csv: Proper redirect added for backward compatibility; will need updating after file rename

Overall Score: 8.7/10

The documentation changes are well-executed with consistent application of the rename across all content. The main concerns are technical (file naming and metadata format) rather than content quality issues. Once the file is properly renamed and the title field is corrected, this will be excellent documentation.

Note: Detailed line-by-line feedback would focus on the file naming mismatch and title format issues mentioned above.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d69bd153d4

ℹ️ 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".

[chatgpt-codex-connector]

Redirect Zenefits URL to an existing article path

This redirect now sends .../connections/Zenefits to .../connections/TriNet, but there is no corresponding TriNet article in this commit (the only file in that hub is still docs/articles/expensify-classic/connections/Zenefits.md). I checked createDocsRoutes.ts, and it builds article hrefs from filenames (filename.replace('.md', '')), so the generated route remains /Zenefits; after deploy, this redirect will forward users to a non-existent page instead of the renamed content.

Useful? React with 👍 / 👎.

[OSBotify]

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

Updated articles:

• articles/expensify-classic/connections/Zenefits
• articles/new-expensify/billing-and-subscriptions/Plan-types-and-pricing