Skip to content

[No QA] Update Add-Approvals.md#72373

Merged
strepanier03 merged 2 commits into
mainfrom
stephanieelliott-patch-19
Oct 20, 2025
Merged

[No QA] Update Add-Approvals.md#72373
strepanier03 merged 2 commits into
mainfrom
stephanieelliott-patch-19

Conversation

@stephanieelliott

Copy link
Copy Markdown
Contributor

@stephanieelliott stephanieelliott self-assigned this Oct 11, 2025
@stephanieelliott stephanieelliott requested a review from a team as a code owner October 11, 2025 05:08
@melvin-bot

melvin-bot Bot commented Oct 11, 2025

Copy link
Copy Markdown

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 @kadiealexander

@melvin-bot melvin-bot Bot requested review from kadiealexander and removed request for a team October 11, 2025 05:08
@melvin-bot

melvin-bot Bot commented Oct 11, 2025

Copy link
Copy Markdown

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

Comment thread docs/articles/new-expensify/workspaces/Add-Approvals.md Outdated
Comment thread docs/articles/new-expensify/workspaces/Add-Approvals.md Outdated
@github-actions

Copy link
Copy Markdown
Contributor

HelpDot Documentation Review

Overall Assessment

This PR makes targeted improvements to the Add-Approvals.md documentation, addressing key formatting issues and enhancing content clarity. The changes focus on correcting punctuation errors, improving step numbering, and adding important plan-specific information that helps users understand feature availability.

Scores Summary

  • Readability: 8/10 - Clear improvements to formatting and step sequences enhance user comprehension
  • AI Readiness: 7/10 - Better keyword coverage and clearer context, though some structural elements could be enhanced
  • Style Compliance: 8/10 - Good adherence to HelpDot standards with proper terminology and formatting

Key Findings

Positive Improvements:

  • Fixed critical punctuation errors (missing periods in steps 1-2 of "Enable Approvals" section)
  • Corrected step numbering sequence in "Set the Default Approval Workflow" (steps 3-6 → 4-7)
  • Enhanced metadata with additional relevant keywords (approval workflow, workspace workflows)
  • Improved description clarity by specifying "expenses" instead of generic "approvals"
  • Added valuable plan-specific guidance for Control plan features
  • Included new FAQ addressing common user question about custom workflows

Areas for Enhancement:

  • Some inconsistent punctuation patterns remain (step 1 in "Set the Default Approval Workflow" section missing period)
  • Could benefit from more descriptive section headings for AI discoverability
  • Navigation instructions could be more specific about UI element locations

Recommendations

Priority 1 (Critical):

  • Fix remaining punctuation inconsistency in step 1 of "Set the Default Approval Workflow" section

Priority 2 (Recommended):

  • Consider adding breadcrumb navigation context for better AI readability
  • Enhance section headings with more descriptive terms (e.g., "Configure Approval Workflows for Your Workspace")

Priority 3 (Optional):

  • Consider adding a brief overview of approval workflow benefits at the beginning
  • Add cross-references to related billing/subscription documentation

Files Reviewed

  • docs/articles/new-expensify/workspaces/Add-Approvals.mdImproved - Meaningful enhancements to formatting, content accuracy, and user guidance

Note: The changes in this PR represent solid improvements to documentation quality, with only minor formatting consistency issues remaining to address.

@github-actions github-actions Bot changed the title Update Add-Approvals.md [No QA] Update Add-Approvals.md Oct 11, 2025
@OSBotify

OSBotify commented Oct 11, 2025

Copy link
Copy Markdown
Contributor

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

Updated articles:

@stephanieelliott

Copy link
Copy Markdown
Contributor Author

@stephanieelliott

Copy link
Copy Markdown
Contributor Author

@kadiealexander bump, can you merge this please?

@strepanier03 strepanier03 left a comment

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.

Reviewed the content and it looks like good changes that will clarify things for customers and AZ.

@strepanier03 strepanier03 merged commit 64c95dd into main Oct 20, 2025
13 of 14 checks passed
@strepanier03 strepanier03 deleted the stephanieelliott-patch-19 branch October 20, 2025 21:07
@melvin-bot melvin-bot Bot added the Emergency label Oct 20, 2025
@melvin-bot

melvin-bot Bot commented Oct 20, 2025

Copy link
Copy Markdown

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

@stephanieelliott

Copy link
Copy Markdown
Contributor Author

Thanks Sheena!

@strepanier03

Copy link
Copy Markdown
Contributor

PR checklist not needed, I removed the emergency label.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/strepanier03 in version: 9.2.35-0 🚀

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

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/blimpich in version: 9.2.35-4 🚀

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

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants