[No QA] Docs updates for E/A#96990 Copy workspace settings help article

[MelvinBot]

Reviewer note: it's expected that the image will not render in the article in the dev view, since it was added in this same PR!

Explanation of Change

#96990 removes the bulkEditWorkspaces beta gate, making the Copy settings option in the Workspaces list three-dot menu available to all eligible Workspace Admins. This feature (copying settings from one workspace onto one or more existing workspaces) had no help site documentation.

This PR adds a new help article documenting the feature:

• docs/articles/new-expensify/workspaces/Copy-Workspace-Settings.md

The article covers who can copy settings, how to run the copy flow (Workspaces → three dots (⋮) → Copy settings → select workspaces → select settings → confirm), which settings can be copied, and what happens after copying. It cross-links to the existing Duplicate Workspace article to distinguish "copy settings to existing workspaces" from "duplicate to create a new workspace."

All UI labels (Copy settings, Next, Select workspaces, Select settings) were verified against the current App source, and the article follows HELPSITE_NAMING_CONVENTIONS.md, HELP_AUTHORING_GUIDELINES.md, and TEMPLATE.md.

Related PR

• [Bulk workspace edits] Remove bulkEditWorkspaces beta gating #96990

---

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

[github-actions]

HelpDot Documentation Review

Overall Assessment
This PR adds a single, well-structured new article, Copy-Workspace-Settings.md, documenting the newly ungated Copy settings feature. It closely follows all three governance specs: clean metadata, task-based headings, correct UI referencing, and precise cross-linking. Quality is high overall, with one load-bearing defect (a typo in the frontmatter title) and a few minor cleanups.

Scores Summary

• Readability: 9/10 - Clear, concise, benefit-focused intro; sequential numbered steps; scannable sections. Minor trailing whitespace on two lines.
• AI Readiness: 9/10 - Strong internalScope (audience/covers/does not cover), realistic keywords, single-workflow focus, correct heading hierarchy (one title heading plus FAQ, only sub-headings for sections), and at least one full 'How to...' heading using the feature name.
• Style Compliance: 8/10 - UI labels verified and bolded (Copy settings, Next, Select workspaces, Select settings); three dots written as three dots (vertical ellipsis); unified navigation phrasing matches the convention exactly. Docked for the frontmatter title typo and Title Case usage.

Key Findings

• Must fix - frontmatter title typo: the YAML title reads 'Copy Workspace Wettings' but should be 'Copy Workspace Settings'. The H1 is correct, but the YAML title feeds SEO and retrieval.
• Positive: Excellent metadata and internalScope; correct single-title plus FAQ structure with only sub-headings for sections; task-based headings (Who/How/What); FAQ entries in proper question form.
• Positive: Cross-links use relative paths and descriptive anchors ('duplicate a workspace', 'differences between the Collect and Control plans'), with no links embedded in numbered steps.
• Positive: Screenshot suggestion uses the exact HTML comment format with a specific, non-generic Purpose.
• Minor: Title and H1 use Title Case ('Copy Workspace Settings') while the actual UI option is Copy settings (Sentence case) - acceptable for an article title but worth aligning.
• Minor: Trailing whitespace on step 4 and the 'Why do not I see the Copy settings option?' answer line.

Recommendations

• Correct the frontmatter title typo (Wettings to Settings) before merge.
• Strip trailing whitespace on the two affected lines.
• Optionally standardize heading phrasing ('in Expensify' appears on one heading but not others).

Files Reviewed

• docs/articles/new-expensify/workspaces/Copy-Workspace-Settings.md - New article, high quality; fix frontmatter title typo before merge.

Note: This is a top-level summary review of the proposed changes.

[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 @greg-schroeder

[melvin-bot]

@mjasikowski @greg-schroeder One of you needs to 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]

[OSBotify]

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

Updated articles:

• articles/new-expensify/workspaces/Copy-Workspace-Settings

[ishpaul777]

we should point to Copy Setting option not the Duplicate Workspace

[MelvinBot]

I looked into the checks — the only failing one is PR Reviewer Checklist / checklist, and there's nothing to fix in code here.

That check fails simply because the reviewer checklist hasn't been completed yet. It's a manual gate that passes once a reviewer fills out the checklist boxes in their review comment, not a CI/test failure caused by the PR's changes.

Every other check (build, verify, validate, spellcheck, etc.) is passing. So there's no code change to push — this will clear on its own once a reviewer completes the checklist.