[No QA] Add beta disclaimer

[sakluger]

Explanation of Change

The Uber 4 Business integration is still in beta. Adding a disclaimer at the top directing people to reach out to Concierge to get set up.

Fixed Issues

https://github.com/Expensify/Expensify/issues/528799

Tests

No Tests

• Verify that no errors appear in the JS console

Offline tests

N/A

QA Steps

Manual QA - review the help doc and verify the text shows up correctly.

// TODO: These must be filled out, or the issue title must include "[No QA]."

• Verify that no errors appear in the JS console

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: mWeb Chrome
  • iOS: Native
  • iOS: mWeb 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 verified there are no new alerts related to the canBeMissing param for useOnyx
• 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 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 used JaimeGPT to get English > Spanish translation. I then posted it 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 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 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.ts 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 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 new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• 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.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user 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.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

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

[melvin-bot]

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

HelpDot Documentation Review

Overall Assessment

This PR adds a beta disclaimer to the Uber for Business integration documentation. The change is minimal but important for setting user expectations. The document itself is well-structured and follows HelpDot standards effectively.

Scores Summary

• Readability: 9/10 - Clear, well-organized content with logical flow. The beta disclaimer is prominently placed and easy to understand.
• AI Readiness: 8/10 - Good use of descriptive headings and proper YAML metadata. The document maintains clear context throughout with specific feature names and navigation paths.
• Style Compliance: 9/10 - Excellent adherence to Expensify documentation standards with proper terminology (workspace, members) and consistent formatting.

Key Findings

Strengths:

• Beta disclaimer is appropriately placed at the top for maximum visibility
• Clear call-to-action (reach out to Concierge) for users wanting access
• Document uses proper heading hierarchy (# and ##)
• Excellent use of step-by-step instructions with specific navigation paths
• Strong FAQ section addressing common user questions
• Proper YAML frontmatter with descriptive metadata and relevant keywords

Minor Observations:

• The beta disclaimer uses bold formatting which is appropriate for visibility
• Consistent use of "New Expensify" vs "Expensify Classic" terminology
• Navigation paths are clear and use the correct UI element names (Workspaces, Receipt partners)
• Good use of contextual information (e.g., "workspace owner is selected by default")

Recommendations

• No changes required - The beta disclaimer is clear, properly formatted, and well-positioned
• The existing document demonstrates strong documentation practices that should be maintained
• Consider this approach for future beta feature documentation

Files Reviewed

• docs/articles/new-expensify/connections/Uber-for-Business.md - Approved. Simple, effective beta disclaimer added with no issues identified.

Overall Quality Score: 8.7/10 - This is a well-executed documentation update for a beta feature.

[github-actions]

Documentation Review Summary

I reviewed the Uber for Business documentation and found some violations that should be addressed:

Issues with Changed Lines (Addressed inline):

✅ Line 9: Beta note formatting - commented inline

Pre-existing Issues in the File:

While these issues exist in lines not changed by this PR, they should be addressed for full HelpDot compliance:

AI Readiness Violations:

• Missing breadcrumb path: The H1 heading "Connect the Uber for Business Integration" (line 11) should have a breadcrumb path below it: Settings > Workspaces > Receipt partners
• Vague pronoun usage (line 44): "We will automatically detect" should specify "Expensify will automatically detect"
• Vague role reference (line 37): "As an admin" should specify the exact role name (e.g., "As a Workspace Admin")

Readability Violations:

• Inconsistent navigation paths: All navigation paths should start with "Settings" for consistency (lines 14, 19, 25, 33, 46, 53)
• Formatting issue (line 48): Parenthetical note should be a separate sentence
• Grammar issue (line 71): Missing period after "i.e." in parenthetical example

Style Compliance:

• Terminology inconsistency (line 61): Consider standardizing references to "New Expensify" vs "Expensify"

These issues don't block the beta note addition, but should be addressed in a follow-up to ensure the documentation meets HelpDot standards.

[OSBotify]

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

Updated articles:

• articles/new-expensify/connections/Uber-for-Business

[melvin-bot]

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

[sakluger]

We're sending out comms today that links to this help doc. The check was the PR reviewer checklist, which was just completed less than an hour ago for the previous commit.

[OSBotify]

🚀 Deployed to staging by https://github.com/sakluger in version: 9.2.43-0 🚀

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

[OSBotify]

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

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