[No QA] [NO QA] Docs updates for E/A#87740 Update attendee column docs for optional sorting

[MelvinBot]

Summary

• Updates Adding-Attendees.md to reflect that Attendees and Per attendee columns are no longer auto-shown in search results — users must enable them via the Columns picker
• Adds documentation that these columns now support sorting
• Updates Managing-Expenses-in-a-Report.md to clarify attendee columns are optional via the Columns picker

Related PR: #87740

[OSBotify]

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

Updated articles:

• articles/new-expensify/reports-and-expenses/Adding-Attendees
• articles/new-expensify/reports-and-expenses/Managing-Expenses-in-a-Report

[melvin-bot]

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

[github-actions]

Naming / UI terminology: "Columns picker" adds the word "picker" which may not match the exact UI label. Per HELPSITE_NAMING_CONVENTIONS.md, use the exact text shown in the product UI — do not add extra words. If the UI button is simply Columns, write "via the Columns button" or "by clicking Columns" instead of "via the Columns picker."

Also, "when attendee tracking is available" is vague — consider stating the specific condition (e.g., "when at least one expense in the report has attendees") for deterministic clarity.

[github-actions]

Step formatting: This paragraph mixes an explanation with procedural steps (lines 51-53). Per HELP_AUTHORING_GUIDELINES.md Section 5, step instructions should be sequential and action-oriented. Consider starting the numbered steps from a clearer entry point — right now the instruction "Go to Reports > Expenses" in step 1 duplicates the path already mentioned in this sentence. You could remove the redundant path reference here or remove step 1 below.

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR updates two articles to reflect changes in how attendee columns are displayed in reports and search results. The changes are focused and well-scoped: metadata is updated to match new content, a previously incorrect # heading is corrected to ##, and new procedural steps are added for enabling attendee columns. The Managing-Expenses article receives a lighter touch, replacing a static column list with a reference to the Columns picker.

Scores Summary

• Readability: 9/10 - The new steps are clear, sequential, and action-oriented. The instructions for enabling columns are concise and easy to follow. Minor note: the sentence "Once enabled, you can click the column header to sort expenses by that column" is clear but slightly passive in construction.
• AI Readiness: 9/10 - Metadata updates are well done: description and keywords now reflect the new column/sort content, and internalScope is updated accordingly. The heading "How to view attendees on a report" is task-based and includes the feature name. The article retains at least one "How to..." heading as required.
• Style Compliance: 9/10 - UI elements (Columns, Attendees, Per attendee amount, Reports > Expenses) are bolded correctly. The heading level fix from # to ## resolves a governance violation (only one # heading allowed per article, plus optional # FAQ). One minor observation: in Managing-Expenses, the phrase "via the Columns picker" uses "via" which is slightly informal -- "using the Columns picker" would be more consistent with the direct, action-oriented tone in the authoring guidelines, but this is not a blocking issue.

Key Findings

• Heading fix (positive): The change from # How to view attendees on a report to ## How to view attendees on a report in Adding-Attendees.md corrects a structural violation. Per Section 4 of the authoring guidelines, only one # heading (the article title) is allowed, plus the optional # FAQ.
• Metadata alignment (positive): Both the description and keywords in Adding-Attendees.md are updated to reflect the new column visibility and sorting content, which improves search retrieval accuracy.
• Consistent cross-file updates (positive): Both articles are updated in tandem -- Managing-Expenses removes the static attendee column listing and points to the Columns picker, while Adding-Attendees provides the detailed how-to. This avoids duplication and keeps each article focused on a single workflow.
• No cross-linking between the two articles: Since Managing-Expenses now references the Columns picker for attendee columns, consider whether a cross-link to the Adding-Attendees article would help readers who want the full procedural steps. Per the cross-linking standards, this would qualify as a "deep-dive explanation" scenario. This is a suggestion, not a requirement.

Recommendations

1. Consider a cross-link from Managing-Expenses to Adding-Attendees for users who want detailed steps on enabling and using attendee columns.
2. Minor wording tweak in Managing-Expenses: "can be enabled via the Columns picker" could read "can be enabled using the Columns picker" for a slightly more direct tone.

Files Reviewed

• Adding-Attendees.md - Metadata updated, heading level corrected from # to ##, new procedural steps added for enabling columns in search results. All changes comply with governance rules.
• Managing-Expenses-in-a-Report.md - Static attendee column entries removed from list, replaced with a reference to the Columns picker. Clean and well-scoped change.

[github-actions]

UI terminology: Verify that Per attendee amount is the exact label shown in the Columns menu. The rest of the article (lines 47, 97 of the other file) refers to it as Per attendee (without "amount"). If the UI label is "Per attendee," use that consistently. If the Columns menu label differs, note the distinction. Per HELPSITE_NAMING_CONVENTIONS.md: "Use the exact text shown in the product UI."

[OSBotify]

🚀 Deployed to staging by https://github.com/stephanieelliott in version: 9.3.70-0 🚀

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

Bundle Size Analysis (Sentry):

• iOS

[OSBotify]

🚀 Deployed to staging by https://github.com/stephanieelliott in version: 9.3.72-0 🚀

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

Bundle Size Analysis (Sentry):

• Android
• iOS

[OSBotify]

🚀 Deployed to production by https://github.com/lakchote in version: 9.3.72-1 🚀

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