Docs updates for E/A#100278 Document automatic #admins room pinning behavior

[MelvinBot]

Explanation of Change

Help site follow-up to #100278, which changed when the #admins room is pinned automatically.

Behavior after that PR: only the first workspace a user creates at sign-up gets its #admins room pinned (that room holds the onboarding tasks). Any workspace created afterwards by someone who already owns a paid workspace does not get its #admins room pinned.

Neither behavior was documented anywhere on the help site, so members had no answer to "why is my #admins room pinned?" or "why isn't my new workspace's #admins room pinned?". This PR documents both:

• docs/articles/new-expensify/chat/Prioritize-and-Pin-Chats.md — adds a ## What chats Expensify pins for you automatically section covering the first-workspace rule, the fact that later workspaces are not pinned, and how to unpin.
• docs/articles/new-expensify/chat/Expensify-Chat-Rooms-for-Admins.md — adds an FAQ entry answering "Why is my #admins room pinned to the top of my inbox?", cross-linked to the pinning article.

Both files also get keyword additions so the new content is retrievable.

Terminology was verified against the live web UI before writing: the room is #admins, the chat action buttons are Pin and Unpin, and the sort setting is Priority mode with the options #focus and Most recent. Pinning behavior itself was also confirmed live — the first workspace's #admins room appeared pinned at the top of the Inbox, and a second workspace's #admins room did not.

The changes follow docs/HELP_AUTHORING_GUIDELINES.md (single # title plus # FAQ, task-based ## headings starting with a question word, no ###), docs/HELPSITE_NAMING_CONVENTIONS.md (bolded UI labels, exact casing), and docs/TEMPLATE.md.

Fixed Issues

$ Help site follow-up to #100278 (part of #99088)
PROPOSAL: N/A

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.

Documentation-only change — no app code is touched. Reviewing means confirming the two articles describe the behavior shipped in #100278.

• Verify that no errors appear in the JS console

Offline tests

N/A — help site content only.

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."
// 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 followed proper code patterns (see Reviewing the code)
  • 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 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)
• 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)
• 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.
• 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

---

@hungvu193, 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.

[MelvinBot]

I created this PR from a branch on Expensify/App rather than your fork, because I don't have push access to hungvu193/App.

To take ownership of this branch and push updates yourself, run:

git remote add upstream https://github.com/Expensify/App.git
git fetch upstream claude-docsAdminRoomPinning
git checkout -b claude-docsAdminRoomPinning upstream/claude-docsAdminRoomPinning
git push -u origin claude-docsAdminRoomPinning

Then you can close this PR and open a new one from your fork. If you'd rather just review the content as-is, no action is needed here.