Skip to content

[No QA] Add Pre-Booking Approval docs to travel help articles - #91355

Merged
kadiealexander merged 6 commits into
mainfrom
claude-preBookingApprovalDocs
May 22, 2026
Merged

kadiealexander merged 6 commits into
mainfrom
claude-preBookingApprovalDocs

Conversation

@MelvinBot

@MelvinBot MelvinBot commented May 21, 2026 •

Copy link
Copy Markdown
Contributor

Explanation of Change

Adds documentation for the new Pre-Booking Approval travel policy feature across two help articles:

Setting-Approval-Types-and-Adding-Members.md:

  • Added Pre-Booking Approval to the list of policy group actions (available for Air, Hotel, and Car)
  • New section explaining the full Pre-Booking Approval traveler workflow
  • New FAQ entries covering availability, expiration, and fare changes
  • Fixed heading levels from ### to ## per HelpDot template standards
  • Replaced "employee/user" with "member" per naming conventions

Approving-Travel.md:

  • New section on how approvers review and approve Pre-Booking Approval requests
  • New section on what to expect after approving (notifications, traveler finalization window)
  • Updated FAQ to include Pre-Booking Approval behavior when no one approves
  • Updated Secondary Approvers section to mention Pre-Booking Approval
  • Fixed heading levels from # to ## for content sections per HelpDot template standards
  • Replaced "employee" with "member" per naming conventions

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/639554

Tests

// TODO: The human co-author must fill out the tests you ran before marking this PR as "ready for review"
// Please describe what tests you performed that validates your changed worked.

  • I reviewed the Files Changed tab - changed are as expected
  • I reviewed the build pages for accuracy - both looked really good

Offline tests

N/A - documentation-only change.

QA Steps

// TODO: The human co-author must fill out the QA tests you ran before marking this PR as "ready for review".
// Please describe what QA needs to do to validate your changes and what areas do they need to test for regressions.

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android / native
    • Android / Chrome
    • iOS / native
    • iOS / Safari
    • MacOS / Chrome / Safari
    • MacOS / Desktop
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
      • If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
  • I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

N/A - documentation-only change.

Android: mWeb Chrome

N/A - documentation-only change.

iOS: Native

N/A - documentation-only change.

iOS: mWeb Safari

N/A - documentation-only change.

MacOS: Chrome / Safari

N/A - documentation-only change.

Update Setting Approval Types and Approving Travel articles to document
the new Pre-Booking Approval group policy action. Includes approver
workflow, post-approval expectations, FAQ entries, and heading level
fixes per HelpDot template standards.

Co-authored-by: Sheena Trepanier <strepanier03@users.noreply.github.com>
@MelvinBot
MelvinBot requested a review from a team May 21, 2026 21:51
@github-actions github-actions Bot changed the title Add Pre-Booking Approval docs to travel help articles [No QA] Add Pre-Booking Approval docs to travel help articles May 21, 2026
@OSBotify

This comment has been minimized.

@strepanier03
strepanier03 marked this pull request as ready for review May 21, 2026 22:57
@melvin-bot

melvin-bot Bot commented May 21, 2026 •

Copy link
Copy Markdown

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 @kadiealexander

@melvin-bot
melvin-bot Bot requested review from kadiealexander and removed request for a team May 21, 2026 22:57
@melvin-bot

melvin-bot Bot commented May 21, 2026

Copy link
Copy Markdown

@kadiealexander 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

Copy link
Copy Markdown
Contributor

HelpDot Documentation Review

Overall Assessment

This PR adds documentation for the new Pre-Booking Approval travel policy feature across two help articles. It also performs significant governance cleanup on the existing content -- fixing heading hierarchies, replacing non-compliant terminology, reformatting FAQ sections, and cleaning up trailing whitespace. The new content is well-structured and clearly explains a multi-step approval workflow. Overall, this is a strong PR that improves both files substantially.

Scores Summary

  • Readability: 9/10 - New content is clear, scannable, and well-organized with sequential numbered steps. The Pre-Booking Approval workflow is explained logically from both the traveler and approver perspectives. One minor note: "How to understand soft vs. hard approval" reads slightly awkwardly compared to a phrasing like "How soft vs. hard approval works."
  • AI Readiness: 7/10 - All headings are now task-based with action verbs or question words, which is excellent. Keywords were updated to include "pre-booking approval." However, both files are missing the internalScope YAML metadata field, which is required per HELP_AUTHORING_GUIDELINES.md Section 3. This field helps define the audience and workflow scope for retrieval systems.
  • Style Compliance: 9/10 - Terminology corrections from "employee/user" to "member" are consistently applied throughout. FAQ sections are reformatted from bold-text to proper ## headings. Heading hierarchy is fixed (removed improper # and ### usage in content sections). Tone improvements include "Yes!" to "Yes." and contractions expanded to formal language.

Key Findings

Positive aspects:

  • Heading hierarchy fixes across both files bring them into compliance -- # content headings demoted to ##, ### promoted to ##, preserving only # [title] and # FAQ as the sole # headings.
  • Consistent terminology updates from "employee" and "user" to "member" align with naming conventions.
  • FAQ sections in Setting-Approval-Types-and-Adding-Members.md converted from bold-text format to proper ## heading format per TEMPLATE.md.
  • New Pre-Booking Approval content is thorough, covering the full lifecycle: request, approval, finalization, expiration, and price buffer behavior.
  • Trailing whitespace cleaned up throughout both files.

Items to address:

  • Missing internalScope in YAML frontmatter for both files. Per HELP_AUTHORING_GUIDELINES.md Section 3, every article must include internalScope specifying the audience, covered workflow, and explicit exclusions. Example: internalScope: Audience is Travel Admins and approvers. Covers approval workflows for travel bookings, does not cover travel policy creation or booking procedures.
  • There is notable content duplication between the two articles regarding the Pre-Booking Approval workflow (both explain the 24-hour windows, price buffer, and step-by-step flow). Per Section 1 of the authoring guidelines, each article should solve one primary workflow. Consider whether the traveler-facing flow detail belongs only in the Setting article and the approver-facing detail only in the Approving article, with cross-links between them.

Recommendations

  1. Add internalScope metadata to both files to satisfy the mandatory YAML requirements and improve AI retrieval precision.
  2. Reduce duplication of Pre-Booking Approval workflow details between the two articles. Each article should own its perspective (approver vs. policy setup) and cross-link to the other for the complementary view.
  3. Consider rephrasing "How to understand soft vs. hard approval" to something like "How soft vs. hard approval works" for more natural readability.

Files Reviewed

  • docs/articles/travel/travel-policy/Approving-Travel.md - New Pre-Booking Approval sections for approvers, heading hierarchy fixes, terminology updates. Well-structured additions.
  • docs/articles/travel/travel-policy/Setting-Approval-Types-and-Adding-Members.md - New Pre-Booking Approval policy setup content, heading fixes (### to ##), FAQ reformatting, terminology updates. Thorough coverage of the feature.

Review based on governance files: HELPSITE_NAMING_CONVENTIONS.md, HELP_AUTHORING_GUIDELINES.md, and TEMPLATE.md.

strepanier03 and others added 3 commits May 21, 2026 17:04
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…Adding-Members.md

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…Adding-Members.md

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@OSBotify

This comment has been minimized.

@strepanier03

Copy link
Copy Markdown
Contributor

Okay this is ready for review!

@OSBotify

This comment has been minimized.

@OSBotify

Copy link
Copy Markdown
Contributor

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

Updated articles:

@kadiealexander

Copy link
Copy Markdown
Contributor

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
    • MacOS: Desktop
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified there are no new alerts related to the canBeMissing param for useOnyx
  • I verified proper code patterns were followed (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp
Android: mWeb Chrome
iOS: HybridApp
iOS: mWeb Safari
MacOS: Chrome / Safari
MacOS: Desktop

@kadiealexander
kadiealexander merged commit 45b2424 into main May 22, 2026
26 checks passed
@kadiealexander
kadiealexander deleted the claude-preBookingApprovalDocs branch May 22, 2026 05:04
@melvin-bot

melvin-bot Bot commented May 22, 2026

Copy link
Copy Markdown

@kadiealexander 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.

@melvin-bot melvin-bot Bot added the Emergency label May 22, 2026

Set this up under:

- Approvers can set their own secondary approver under **User icon** > **My profile** > **Configuration** > **Approval Settings**. Click Add Approver to designate a secondary approver who can approve on your behalf. You may add multiple secondary approvers.

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.

Button naming violation: "Click Add Approver" should bold the button name to match the button naming standards. The second bullet in this same section correctly bolds Add approver, but this first bullet does not.

Suggested fix: Click **Add Approver** to designate a secondary approver...

@github-actions

Copy link
Copy Markdown
Contributor

HelpDot Documentation Review

Overall Assessment

This PR makes strong, governance-aligned improvements to two travel documentation files. The changes add Pre-Booking Approval content, fix heading hierarchy (eliminating # and ### misuse), convert headings to task-based format, add required internalScope metadata, correct terminology ("member" instead of "employee"/"user"), restructure FAQ sections to use proper ## headings, and clean up trailing whitespace. The quality of the proposed changes is high overall.

Scores Summary

  • Readability: 9/10 - Steps are clear, sequential, and action-oriented. The new Pre-Booking Approval sections are well-structured with numbered steps that follow the actual user flow. One heading ("How to understand soft vs. hard approval") reads slightly awkwardly but is functional.
  • AI Readiness: 10/10 - Both files now include internalScope with audience, scope, and exclusions. All headings are task-based with action verbs or question words. Multiple "How to..." headings per article. Keywords updated to include "pre-booking approval." Heading hierarchy uses only # (title) and ## throughout, with ### correctly eliminated.
  • Style Compliance: 9/10 - Terminology corrections from "employee"/"user" to "member" are consistent and correct. FAQ sections properly restructured from bold-inline format to ## headings per TEMPLATE.md. One button reference ("Click Add Approver" in the secondary approvers section of Approving-Travel.md) is missing bold formatting -- should be "Click Add Approver" per button naming standards. The exclamation mark ("Yes!") was correctly changed to a period.

Key Findings

  • All # content headings (other than title and FAQ) were correctly demoted to ##, and all ### headings were promoted to ##, bringing both files into full heading hierarchy compliance.
  • Every changed heading now follows task-based formatting with action verbs or question words -- a significant improvement from the noun-only and topic-only headings that existed before.
  • The internalScope metadata additions are well-written, clearly defining audience, covered scope, and explicit exclusions.
  • Terminology is consistently corrected throughout: "employee" and "user" replaced with "member," "employee's" replaced with "member's."
  • The FAQ section in Setting-Approval-Types-and-Adding-Members.md was restructured from bold-text-with-line-break format to proper ## question headings, matching TEMPLATE.md requirements.
  • Internal jargon ("spotnana policy") was removed from keywords -- good alignment with the rule to avoid internal language.
  • Pre-Booking Approval content is thorough and includes both the traveler-facing flow and the approver-facing flow, split appropriately across the two articles.

Recommendations

  1. Bold the "Add Approver" button name in Approving-Travel.md. The line under "How to set up secondary approvers" reads: "Click Add Approver to designate a secondary approver..." This should be "Click Add Approver to designate a secondary approver..." per button naming standards.
  2. Consider rephrasing "How to understand soft vs. hard approval" to something like "How soft and hard approval work" -- the current phrasing is compliant but reads slightly unnaturally. This is a minor suggestion, not a blocker.
  3. Minor content duplication: Both files describe the Pre-Booking Approval 24-hour window and price buffer. This is acceptable given the different audiences (approvers vs. admins), but worth noting in case future edits create drift between the two descriptions.

Files Reviewed

  • docs/articles/travel/travel-policy/Approving-Travel.md - Heading hierarchy fixed, task-based headings applied, Pre-Booking Approval content added, terminology corrected, FAQ answers cleaned up. Strong improvements.
  • docs/articles/travel/travel-policy/Setting-Approval-Types-and-Adding-Members.md - Heading depth fixed (### to ##), task-based headings applied, Pre-Booking Approval section and FAQ entries added, FAQ restructured to proper format, terminology corrected throughout. Strong improvements.

Note: Detailed line-by-line feedback has been provided as inline comments.

@OSBotify OSBotify mentioned this pull request May 22, 2026
71 tasks done
@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/kadiealexander in version: 9.3.80-0 🚀

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

Bundle Size Analysis (Sentry):

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/luacmartins in version: 9.3.81-2 🚀

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants