Skip to content

[No QA] Update Delete-Expenses.md to clarify who can take actions #71865

Merged
stephanieelliott merged 1 commit into
mainfrom
stephanieelliott-patch-19
Oct 9, 2025
Merged

[No QA] Update Delete-Expenses.md to clarify who can take actions #71865
stephanieelliott merged 1 commit into
mainfrom
stephanieelliott-patch-19

Conversation

@stephanieelliott

Copy link
Copy Markdown
Contributor

@stephanieelliott stephanieelliott self-assigned this Oct 5, 2025
@stephanieelliott stephanieelliott requested a review from a team as a code owner October 5, 2025 18:30
@melvin-bot

melvin-bot Bot commented Oct 5, 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 @Christinadobrzyn

@melvin-bot melvin-bot Bot requested review from Christinadobrzyn and removed request for a team October 5, 2025 18:31
@melvin-bot

melvin-bot Bot commented Oct 5, 2025

Copy link
Copy Markdown

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

Company card expenses can’t be deleted if **Allow deleting transactions** is disabled for that card. If that's the case, only a Domain Admin can enable this setting—or unassign the card to remove draft expenses.
Company card expenses can’t be deleted if **Allow deleting transactions** is turned off for that card. In that case, only a Domain Admin can enable this setting—or unassign the card to remove draft expenses.

Expense actions like deleting, editing, or retracting can only be done in your own account. Even Workspace Admins can’t delete another member’s expenses. If you need to help a teammate, ask them to add you as a [Copilot](https://help.expensify.com/articles/new-expensify/settings/Copilot-Access) so you can assist from their account.

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.

Terminology violation: Use 'member' instead of 'teammate' to match Expensify style standards. Change 'teammate' to 'member' for consistency.

@github-actions

github-actions Bot commented Oct 5, 2025

Copy link
Copy Markdown
Contributor

HelpDot Documentation Review

Overall Assessment

This PR makes a focused improvement to the Delete-Expenses.md article by adding crucial clarification about account-level limitations for expense actions. The changes directly address user confusion about who can delete, edit, or retract expenses, with the addition providing valuable context about the Copilot workaround.

Scores Summary

  • Readability: 8/10 - The new content flows well and is written in clear, accessible language. The addition integrates naturally with the existing FAQ structure.
  • AI Readiness: 8/10 - Good metadata update in description, content provides clear context, though the addition could benefit from a more descriptive subheading.
  • Style Compliance: 9/10 - Excellent adherence to Expensify style guidelines with proper terminology ("Workspace Admins" vs "members"), appropriate tone, and correct link formatting.

Key Findings

  • Positive: The addition significantly improves user understanding by explaining a common point of confusion about permission limitations
  • Positive: Proper use of Expensify terminology ("Workspace Admins," "members," "teammates")
  • Positive: Well-integrated cross-reference to Copilot functionality with proper link formatting
  • Minor: The metadata description update is helpful but could be more specific about the type of account-level limitations

Recommendations

  • Consider adding a more descriptive subheading if this content grows (currently works well within existing FAQ structure)
  • The changes successfully address the user confusion mentioned in the Slack thread
  • No critical issues identified - this is a well-executed documentation improvement

Files Reviewed

  • docs/articles/new-expensify/reports-and-expenses/Delete-Expenses.md: ✅ High-quality addition with proper style compliance and clear user value

Note: This is a summary review. The changes are well-implemented and improve documentation clarity without introducing any style or structural issues.

@github-actions github-actions Bot changed the title Update Delete-Expenses.md to clarify who can take actions [No QA] Update Delete-Expenses.md to clarify who can take actions Oct 5, 2025
@OSBotify

OSBotify commented Oct 5, 2025

Copy link
Copy Markdown
Contributor

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

Updated articles:

@Christinadobrzyn

Copy link
Copy Markdown
Contributor

Looks good!

@stephanieelliott stephanieelliott merged commit 332616e into main Oct 9, 2025
10 of 11 checks passed
@stephanieelliott stephanieelliott deleted the stephanieelliott-patch-19 branch October 9, 2025 21:49
@melvin-bot melvin-bot Bot added the Emergency label Oct 9, 2025
@melvin-bot

melvin-bot Bot commented Oct 9, 2025

Copy link
Copy Markdown

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

@OSBotify

Copy link
Copy Markdown
Contributor

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

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

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/mountiny in version: 9.2.29-5 🚀

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