[No QA] Docs updates for E/A#92116 Travel toggle locks while Travel Invoicing is on

[MelvinBot]

Explanation of Change

App PR #92116 locks the Travel toggle in Workspace settings → More features whenever Travel Invoicing is enabled. An admin can no longer turn Travel off directly — pressing the locked toggle opens a message explaining that Travel Invoicing must be turned off first, with a Go to Travel settings button.

This is a new, user-facing constraint that wasn't documented on the help site, so a Workspace Admin who hits the locked toggle currently has nothing to search for. This PR documents the dependency in the two relevant Travel articles:

• Enable Expensify Travel on a workspace — adds a ## Why can’t I turn off Travel? FAQ with the exact steps to turn off Travel Invoicing first, then Travel.
• Enable Travel Invoicing on a Workspace — adds a bullet to What happens after you enable Travel Invoicing noting that the Travel toggle is locked while Travel Invoicing is on.

All UI labels (More features, Travel, Go to Travel settings, Travel Invoicing) were verified against src/languages/en.ts and follow HELPSITE_NAMING_CONVENTIONS.md, HELP_AUTHORING_GUIDELINES.md, and TEMPLATE.md.

Fixed Issues

Related to #92116
$
PROPOSAL:

Tests

Documentation-only change. No code was modified.

• Verify that no errors appear in the JS console

Offline tests

N/A — documentation-only change.

QA Steps

Documentation-only change. No code was modified.

• Verify that no errors appear in the JS console

---

@blimpich, please review the files changed and confirm they reflect the current behavior. Then mark this PR Ready for review.

[MelvinBot]

Failing check: build (Deploy ExpensifyHelp) — CI infrastructure, not this PR

Root cause: The Install pcregrep step fails with E: Unable to locate package pcregrep on the blacksmith-2vcpu-ubuntu-2404 runner. The step runs sudo apt-get install -y pcregrep with no preceding apt-get update, so a stale/empty apt package index makes the package unresolvable. This is unrelated to the documentation changes in this PR.

Evidence it's environmental (not this PR):

• Every pull_request run of this workflow since ~18:19 UTC today is failing the same way — docs-intacct-travel-invoicing-cr, melvin-docs-auditor-readonly-workspace, claude-docs-qbo-travel-invoicing-cr, docs-xero-travel-invoicing-cr, and this branch.
• push runs to main at 15:05 UTC and earlier today succeeded using the identical step, which proves pcregrep is installable on this runner — the apt index just needs refreshing.

Fix: Run apt-get update before the install in .github/workflows/deployExpensifyHelp.yml:40-41:

      - name: Install pcregrep
        run: |
          sudo apt-get update
          sudo apt-get install -y pcregrep

⚠️ I can't push this fix. My token lacks the workflow scope, so GitHub rejects any push that modifies a file under .github/workflows/ (refusing to allow a Personal Access Token to create or update workflow ... without 'workflow' scope). Because this affects every docs PR right now, the cleanest path is a small standalone infra PR with the one-line change above, made by someone whose credentials have workflow scope. Once that lands on main, re-running this PR's build check will pass.

[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]

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

[github-actions]

Non-standard action verb: "When you press the locked toggle" uses "press", which is not a standard action verb in HelpDot articles. Per HELPSITE_NAMING_CONVENTIONS.md, use Click (web) or Tap (mobile). Since this sentence is platform-neutral, consider rephrasing to: "When you click the locked toggle, a message appears..."

[github-actions]

Non-standard action verb: "Press the locked Travel toggle" uses "press" instead of the standard "Click" / "Tap". Per HELPSITE_NAMING_CONVENTIONS.md, always use exact standard verbs. Consider:

Suggested change

	4. Press the locked **Travel** toggle, then click **Go to Travel settings**.
	4. Click the locked **Travel** toggle, then click **Go to Travel settings**.

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR adds a new FAQ entry to the Enable Travel article explaining why the Travel toggle may be locked (due to Travel Invoicing), and adds a corresponding bullet point to the Travel Invoicing article noting the same behavior. The changes are small, well-scoped, and generally well-written. They address a real user question with clear, actionable steps.

Scores Summary

• Readability: 9/10 - The new FAQ answer is clear, concise, and scannable. Steps are sequential and action-oriented. The bullet point addition in the Travel Invoicing article is direct and easy to understand.
• AI Readiness: 9/10 - The FAQ heading "Why can't I turn off Travel?" is question-based and matches real search intent. It uses the exact feature name. No metadata changes were needed since this is an addition to existing articles with valid YAML frontmatter.
• Style Compliance: 8/10 - UI elements are correctly bolded (Travel, More features, Travel Invoicing, Go to Travel settings). Navigation instructions use the correct unified format. One minor issue noted below.

Key Findings

• The FAQ heading follows governance rules: it starts with a question word ("Why") and is task/feature-specific.
• UI element bolding is consistently applied throughout the new content.
• The navigation instruction in step 1 correctly uses the unified format: "on the left on web, and at the bottom on mobile" -- though note the governance file specifies "on the bottom on mobile" without "and at the", this is a very minor stylistic variance and reads naturally.
• Cross-linking at the end uses the recommended "Learn more about [Feature Name]" anchor text pattern and a relative link, both compliant with cross-linking standards.
• The link is correctly placed after the procedural steps, not within them.
• Step 1 uses "click" for Workspaces, which is appropriate. Steps are sequential and aligned with the actual UI flow.
• Minor style note: Step 4 uses "Press the locked Travel toggle" while step 1 uses "click." The governance files do not mandate a specific verb for toggles, but consistency within a single set of steps would be ideal. Consider using "click" throughout for consistency, or "tap" if this is specifically for mobile. The mixed use of "press" and "click" may cause slight confusion.

Recommendations

• Consider standardizing the verb in step 4 from "Press" to "Click" to match the verb used in the other steps within the same instruction set. The word "press" appears only once across the new content and diverges from the "click" convention used elsewhere.
• No other changes are strictly required. The content is well-structured and governance-compliant.

Files Reviewed

• docs/articles/travel/company-setup/Enable-Travel-on-a-Workspace.md - New FAQ entry added ("Why can't I turn off Travel?"). Well-structured with clear steps and proper cross-link.
• docs/articles/travel/travel-invoicing/Enable-Travel-Invoicing-in-a-Workspace.md - New bullet point added explaining the locked Travel toggle behavior. Concise and informative.

Note: This review covers only the proposed changes in the diff, not pre-existing content.

[OSBotify]

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

Updated articles:

• articles/travel/company-setup/Enable-Travel-on-a-Workspace
• articles/travel/travel-invoicing/Enable-Travel-Invoicing-in-a-Workspace

[OSBotify]

🚀 Deployed to staging by https://github.com/stephanieelliott in version: 9.4.8-0 🚀

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

Bundle Size Analysis (Sentry):

• iOS

[OSBotify]

🚀 Deployed to staging by https://github.com/stephanieelliott in version: 9.4.8-0 🚀

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

Bundle Size Analysis (Sentry):

• Android
• iOS

[OSBotify]

🚀 Deployed to production by https://github.com/puneetlath in version: 9.4.8-3 🚀

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