[No QA] Create Find-Rooms-in-a-Workspace.md

[stephanieelliott]

Added documentation on how to find and access rooms in a workspace using the Rooms directory, including user permissions and navigation steps.

We'll plan to time the merge with #93416

Explanation of Change

Fixed Issues

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

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR adds one new article, docs/articles/new-expensify/chat/Find-Rooms-in-a-Workspace.md, covering how members and admins find and access rooms via the Rooms directory. It is a single, well-scoped workflow that closely follows the HelpDot governance standards. Quality is high with only minor polish items.

Scores Summary

• Readability: 9/10 - Clear, concise, scannable sentences with sequential numbered steps and a focused FAQ.
• AI Readiness: 9/10 - Complete YAML metadata (including internalScope), task-based headings, full feature name ("Rooms directory") used consistently, and correct #/## hierarchy.
• Style Compliance: 8/10 - Buttons/tabs are bolded and use the unified navigation phrasing per conventions; a couple of small formatting nits remain.

Key Findings

• Strong adherence to Section 4 structure: exactly one # title plus # FAQ, all content under task-based ## headings, no ### or deeper.
• All section headings start with an action verb or question word ("Who can use...", "How to find...", "What happens after..."), satisfying the strict heading rules.
• Navigation correctly uses the unified sentence "In the navigation tabs (on the left on web, on the bottom on mobile)" from HELPSITE_NAMING_CONVENTIONS.
• Screenshot placeholder uses the required non-rendered HTML comment format and is placed appropriately.
• Single-workflow scope is respected; admin vs. member differences are explained without expanding into room creation/management (correctly excluded in internalScope).
• Minor: trailing whitespace on a few lines (the "How to find workspace rooms" heading and the "displays the rooms you can access" paragraph).
• Minor: Step 1 embeds a placeholder inside bold (**Workspaces > [Workspace name]**); consider Click **Workspaces**, then select your workspace. for cleaner UI-exact phrasing.

Recommendations

• Trim trailing whitespace on affected lines.
• Optionally split the combined **Workspaces > [Workspace name]** into a UI-exact action plus a plain-text selection of the workspace name.
• No blocking issues; this is publish-ready after the cosmetic cleanup.

Files Reviewed

• docs/articles/new-expensify/chat/Find-Rooms-in-a-Workspace.md - New article, compliant and high quality; minor formatting polish suggested.

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

[stephanieelliott]

Applied all relevant QA bot changes

[OSBotify]

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

Updated articles:

• articles/new-expensify/chat/Find-Rooms-in-a-Workspace

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

[melvin-bot]

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