Skip to content

[No QA] Update Enable-Travel-on-a-Workspace.md to for Add trip names to expenses - #83524

Merged
strepanier03 merged 2 commits into
mainfrom
helpsite-add-trip-names
Feb 26, 2026
Merged

strepanier03 merged 2 commits into
mainfrom
helpsite-add-trip-names

Conversation

@stephanieelliott

Copy link
Copy Markdown
Contributor

Update for this product change: #80019

add Add trip names to expenses
@github-actions

Copy link
Copy Markdown
Contributor

HelpDot Documentation Review

Overall Assessment

This PR adds a single FAQ entry to the "Enable Travel on a Workspace" article, explaining the Add trip names to expenses toggle. The addition is well-scoped, clearly written, and directly addresses a user question that would naturally arise from the product change in #80019. The new content fits naturally within the existing FAQ section and follows the established patterns of the file.

Scores Summary

  • Readability: 9/10 - The new FAQ entry is clear, concise, and well-structured. The question heading is phrased from the user's perspective ("Why are trip names being added to my expense descriptions?"), which is effective for discoverability. The answer progresses logically: what the feature does, how to control it, and a platform-specific caveat. The reading level is appropriate and jargon-free.
  • AI Readiness: 7/10 - The FAQ heading is descriptive and task-oriented, which is good. However, the file's YAML frontmatter is missing an internalScope field (e.g., Audience is Workspace Admins. Covers enabling Expensify Travel and the Add trip names to expenses setting. Does not cover booking restrictions or travel policy configuration.). This is a pre-existing gap in the file rather than something introduced by this PR, but it is worth noting since the new content adds a distinct subtopic. The heading hierarchy is correct (## under # FAQ).
  • Style Compliance: 8/10 - The entry uses bold formatting for UI element names (Add trip names to expenses, Workspaces > [Workspace Name] > Travel), which aligns with Expensify documentation conventions. Terminology is correct ("Workspace Admins", "New Expensify", "Classic"). One minor observation: the "Note:" prefix on the final line could be formatted more consistently with HelpDot patterns -- some articles use a blockquote (>) or simply integrate the caveat into the preceding paragraph. This is a minor stylistic preference rather than an error.

Key Findings

  • The FAQ question is phrased in a way users would naturally ask it, which aids both human scanning and AI retrieval.
  • The three-paragraph structure (what it does / how to toggle it / cross-platform note) is well-organized and gives a complete answer without overloading.
  • The mention that the setting "only appears in New Expensify, but it controls description behavior for both New Expensify and Classic expenses" is a valuable detail that preempts a common follow-up question.
  • The placement of this FAQ entry before the existing "Can I set up travel policy rules..." entry is logical, as it addresses a more specific and potentially confusing behavior.

Recommendations

  1. (Low priority) Consider whether the "Note:" line would read more naturally if integrated into the preceding paragraph or formatted as a blockquote for visual distinction. For example: > **Note:** Add trip names to expenses only appears in New Expensify, but it controls description behavior for both New Expensify and Classic expenses.
  2. (Low priority, pre-existing) The file's YAML frontmatter lacks an internalScope field. If updating the frontmatter is in scope for this PR, adding one would improve AI readiness. Suggested value: internalScope: "Audience is Workspace Admins. Covers enabling Expensify Travel and the Add trip names to expenses setting. Does not cover booking restrictions or travel policy configuration."
  3. (Nitpick) The PR title contains a minor grammatical artifact: "Update Enable-Travel-on-a-Workspace.md to for Add trip names to expenses." This does not affect the documentation itself but is worth cleaning up for PR history clarity.

Files Reviewed

  • docs/articles/travel/company-setup/Enable-Travel-on-a-Workspace.md -- 8 lines added, 0 removed. New FAQ entry for the "Add trip names to expenses" toggle. Clean addition with no issues in the changed lines.

This review assessed only the proposed changes in the diff, not pre-existing content.

@github-actions github-actions Bot changed the title Update Enable-Travel-on-a-Workspace.md to for Add trip names to expenses [No QA] Update Enable-Travel-on-a-Workspace.md to for Add trip names to expenses Feb 26, 2026
@OSBotify

OSBotify commented Feb 26, 2026 •

Copy link
Copy Markdown
Contributor

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

Updated articles:

@strepanier03 strepanier03 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice solid update. I reviewed the change and the build, both look good with proper formatting and navigation.

@strepanier03
strepanier03 merged commit 09cf33f into main Feb 26, 2026
13 checks passed
@strepanier03
strepanier03 deleted the helpsite-add-trip-names branch February 26, 2026 16:54
@OSBotify

Copy link
Copy Markdown
Contributor

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

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

@OSBotify

OSBotify commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/blimpich in version: 9.3.27-8 🚀

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants