Skip to content

[No QA] Docs updates for E/A#103652 Add Join my company workspace onboarding option - #103991

Merged
stephanieelliott merged 2 commits into
mainfrom
claude-docsJoinCompanyWorkspaceOnboarding
Oct 19, 2026
Merged

stephanieelliott merged 2 commits into
mainfrom
claude-docsJoinCompanyWorkspaceOnboarding

Conversation

@MelvinBot

Copy link
Copy Markdown
Contributor

Explanation of Change

Updates the help site for the new Join my company workspace onboarding option, added in Add the join-workspace onboarding intent and Concierge follow up tasks. The option has no beta gate, so all users who reach What do you want to do today? can see it.

  • New feature: Join my company workspace. Join-your-company's-workspace.md only described joining by admin invite. It now has three short steps for finding the workspace yourself during account setup.
  • Incorrect sentence: Troubleshoot-Adding-Your-Work-Email.md said: "Once you click Skip or Got it, the step doesn’t appear again — add the address you want as a contact method after setup instead." That's no longer true. Choosing Join my company workspace reopens What’s your work email?, and skipping it creates an Add your work email Concierge task that links back to the step. The sentence now names both cases.

Labels were checked against src/languages/en.ts and the live web UI (What do you want to do today?, Join my company workspace, What’s your work email?, Skip, Join now, Ask to join, Add your work email).

@carlosmiceli, please review the files changed and confirm they reflect the current behavior. Then post a new comment saying @MelvinBot mark this PR as ready for review.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/672346
PROPOSAL:

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.

  • Verify that no errors appear in the JS console

Offline tests

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.

  • 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
  • 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 any copy / text that was added to the app 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)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • 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)
  • 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 the PR adds or modifies the UI:
    • I asked an AI agent to review the changes for accessibility issues and addressed its findings.
    • I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
    • I verified all new/changed elements have meaningful accessible names and roles.
    • I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
  • 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

Co-authored-by: Carlos Miceli <carlosmiceli@users.noreply.github.com>
@MelvinBot
MelvinBot requested a review from a team October 14, 2026 13:32
@MelvinBot MelvinBot added the HelpDot Apply this label if the issue relates to ExpensifyHelp label Oct 14, 2026
@github-actions github-actions Bot changed the title Docs updates for E/A#103652 Add Join my company workspace onboarding option [No QA] Docs updates for E/A#103652 Add Join my company workspace onboarding option Oct 14, 2026
@OSBotify

This comment has been minimized.

@garrettmknight
garrettmknight marked this pull request as ready for review October 19, 2026 12:33
@melvin-bot

melvin-bot Bot commented Oct 19, 2026

Copy link
Copy Markdown

Product 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?

cc @heyjennahay

@melvin-bot
melvin-bot Bot requested a review from heyjennahay October 19, 2026 12:33
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-19T12:38:16.359218Z 198b829 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@melvin-bot
melvin-bot Bot removed the request for review from a team October 19, 2026 12:33
@melvin-bot

melvin-bot Bot commented Oct 19, 2026

Copy link
Copy Markdown

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

If you're signing up without an invite, select **Join my company workspace** when asked **What do you want to do today?** After you add and verify your work email, Expensify shows the workspaces at your company that you can join. Click **Join now**, or **Ask to join** if the workspace needs admin approval.
If you're creating your Expensify account, you can also find your company's workspace yourself:

1. When asked **What do you want to do today?**, choose **Join my company workspace**.

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.

Naming violation (select vs choose): Use select here, not choose. Per HELPSITE_NAMING_CONVENTIONS.md, choose is only for deciding between options; activating a UI element/option like Join my company workspace should use select. Suggest: "select Join my company workspace".

## Can I try a different work email on the same account?

Yes, while the work email step is still open. If the message appears under the field, correct the address and click **Add work email** again. Once you click **Skip** or **Got it**, the step doesn’t appear again — add the address you want as a contact method after setup instead.
Yes, while the work email step is still open. If the message appears under the field, correct the address and click **Add work email** again. Once you click **Skip** or **Got it**, the step only appears again if you choose **Join my company workspace** during setup or open the **Add your work email** task from Concierge. Otherwise, add the address you want as a contact method after setup instead.

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.

Naming violations in modified line: Per HELPSITE_NAMING_CONVENTIONS.md, do not use click — use select (e.g., "select Add work email", "select Skip or Got it"). Also choose **Join my company workspace** should be select since it activates a UI option, not a decision between options.

@github-actions

Copy link
Copy Markdown
Contributor

HelpDot Documentation Review

Overall Assessment

This PR makes two small, targeted content edits in the New Expensify "Getting started" hub. It documents the self-serve path for joining a company workspace (including the new Join my company workspace / Skip / Concierge task behavior) and updates a related FAQ answer in the work-email troubleshooting article. Both changes are accurate, scoped to a single workflow, and improve clarity. The edits themselves are largely compliant; the main gaps are inherited from surrounding content rather than introduced here.

Scores Summary

  • Readability: 9/10 - The paragraph-to-numbered-steps conversion in the Join article is a clear improvement in scannability. The FAQ sentence is slightly long but accurate.
  • AI Readiness: 8/10 - Changes use full feature names and exact UI labels; the Troubleshoot file has complete YAML including internalScope. The added text in the Join article reads well for retrieval.
  • Style Compliance: 7/10 - New text correctly applies choose for the decision (choose Join my company workspace), Select for buttons, bolded UI labels, and lowercase workspace. Main deduction: the edited FAQ line retains "click Add work email" and "click Skip" (prohibited verb per naming conventions).

Key Findings

  • Positive: New numbered steps in the Join article follow step-formatting standards (sequential, action-oriented, bold labels, correct choose vs Select usage).
  • Positive: Both diffs use exact UI terminology (Join my company workspace, Ask to join, Join now, Add your work email, Skip, Got it) and lowercase generic workspace.
  • To address: The modified FAQ line uses "click" ("click Add work email", "click Skip or Got it"). Conventions require select (or choose for decisions); update to select since the line is being changed anyway.
  • Context (not introduced by this PR, so not scored against the diff): the Join article uses multiple top-level section headings and "Step 1:"-style headings and "Click ... on the left-hand navigation menu," which conflict with current heading/navigation rules.

Recommendations

  • Priority: Replace "click" with "select" in the edited FAQ sentence of Troubleshoot-Adding-Your-Work-Email.md.
  • Suggestion: Confirm "enter the code sent to it" matches the exact in-product wording for the verification step; consider "enter the verification code" if that mirrors the UI.
  • Optional: If the Join article is revisited later, align its top-level section headings and navigation phrasing with the governance rules (out of scope for this PR).

Files Reviewed

  • docs/articles/new-expensify/getting-started/Join-your-companys-workspace.md - Paragraph converted to compliant numbered steps; good.
  • docs/articles/new-expensify/getting-started/Troubleshoot-Adding-Your-Work-Email.md - FAQ answer accurate and mostly compliant; fix retained click usages.

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

@OSBotify

Copy link
Copy Markdown
Contributor

@dylanexpensify
dylanexpensify self-requested a review October 19, 2026 12:40
@stephanieelliott
stephanieelliott removed the request for review from heyjennahay October 19, 2026 19:12
@stephanieelliott
stephanieelliott merged commit c061fca into main Oct 19, 2026
28 of 30 checks passed
@stephanieelliott
stephanieelliott deleted the claude-docsJoinCompanyWorkspaceOnboarding branch October 19, 2026 19:13
@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/stephanieelliott in version: 9.5.15-1 🚀

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

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/grgia in version: 9.5.15-3 🚀

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

Bundle Size Analysis (Sentry):

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

Labels

HelpDot Apply this label if the issue relates to ExpensifyHelp

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants