Skip to content

[No QA] Update help docs for Releases 1-4: Expensify Card Spend Rules#92580

Merged
clarajones-expensify merged 9 commits into
mainfrom
claude-ecardSpendRulesHelpDocs
Jun 13, 2026
Merged

[No QA] Update help docs for Releases 1-4: Expensify Card Spend Rules#92580
clarajones-expensify merged 9 commits into
mainfrom
claude-ecardSpendRulesHelpDocs

Conversation

@MelvinBot

Copy link
Copy Markdown
Contributor

Explanation of Change

This PR adds the help site documentation for the Expensify Card Spend Rules feature, consolidating the resource updates for all four releases (Releases 1–4) into a single set of article changes.

Spend Rules let Workspace Admins approve or decline Expensify Card transactions in real time at the point of sale, before any expense is created. Because the feature is conceptually distinct from both card setup (limits/issuance) and post-submission expense rules, it gets a dedicated article, with light cross-references added to the existing card articles for discoverability.

New article

  • docs/articles/new-expensify/expensify-card/Expensify-Card-Spend-Rules.md — covers default protections, Block rules, Allow rules, evaluation order, editing/deleting rules, applying a rule at card issuance, and the search filter (admin workflow).

Updated articles

  • Set-Up-and-Manage-the-Expensify-Card.md — notes that a Spend Rule can be applied when issuing a card, and that default protections + Spend Rules exist, with a link to the new article.
  • Cardholder-Settings-and-Features.md — adds a "View Spend Rules on Your Card" section and adds Spend Rule restrictions (with Concierge decline notifications) as a decline reason.
  • Troubleshoot-Expensify-Card-issues.md — adds a "Transaction declined by a Spend Rule" troubleshooting subsection.
  • Expensify-Card-Notifications.md — documents the Concierge notification a cardholder receives when a Spend Rule declines a transaction.

Note

This feature is being built across Releases 1–4 and the docs describe its end state. UI labels (e.g., the Spend section, Add card rule, Contains/Exact match, the Workspace > Rules and Wallet > Card Details entry points) are taken from the design doc and should be verified against the shipped product before merge.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/641928

Tests

// TODO: The human co-author must fill out the tests they ran before marking this PR as "ready for review".
// Please describe what tests you performed that validate the help docs render correctly and the content is accurate.

  • Verify the new Expensify Card Spend Rules article renders with the correct title, headings, and cross-links.
  • Verify the four updated card articles render correctly and their new Spend Rules cross-links resolve.

Offline tests

N/A — help site documentation change only.

QA Steps

// TODO: The human co-author must fill out the QA steps before marking this PR as "ready for review", or add "[No QA]" to the title if appropriate for a docs-only change.

  • Verify that no errors appear in the JS console

Add a new Spend Rules article covering default protections, Block rules,
Allow rules, evaluation order, rule management, and search. Cross-reference
Spend Rules from the card setup, cardholder, troubleshooting, and
notifications articles.

Co-authored-by: Stephanie Elliott <stephanieelliott@users.noreply.github.com>
@MelvinBot MelvinBot requested a review from a team June 3, 2026 20:06
@github-actions github-actions Bot changed the title Update help docs for Releases 1-4: Expensify Card Spend Rules [No QA] Update help docs for Releases 1-4: Expensify Card Spend Rules Jun 3, 2026
@OSBotify

This comment has been minimized.

@OSBotify

This comment has been minimized.

@OSBotify

This comment has been minimized.

@stephanieelliott stephanieelliott marked this pull request as ready for review June 6, 2026 01:23
@stephanieelliott stephanieelliott self-requested a review as a code owner June 6, 2026 01:23
@melvin-bot

melvin-bot Bot commented Jun 6, 2026

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

@melvin-bot melvin-bot Bot requested a review from zanyrenney June 6, 2026 01:23
@melvin-bot

melvin-bot Bot commented Jun 6, 2026

Copy link
Copy Markdown

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

@melvin-bot melvin-bot Bot removed the request for review from a team June 6, 2026 01:23
@stephanieelliott stephanieelliott changed the title [No QA] Update help docs for Releases 1-4: Expensify Card Spend Rules [No QA] [Hold for feature] Update help docs for Releases 1-4: Expensify Card Spend Rules Jun 6, 2026
@stephanieelliott stephanieelliott removed the request for review from zanyrenney June 6, 2026 01:23
@stephanieelliott

Copy link
Copy Markdown
Contributor

Copy is good, just need to test the UI steps to confirm they're right - will just before release when it is on staging.

@OSBotify

This comment has been minimized.

Comment thread docs/articles/new-expensify/expensify-card/Cardholder-Settings-and-Features.md Outdated
Comment thread docs/articles/new-expensify/expensify-card/Cardholder-Settings-and-Features.md Outdated
Comment thread docs/articles/new-expensify/expensify-card/Expensify-Card-Spend-Rules.md Outdated
Comment thread docs/articles/new-expensify/expensify-card/Expensify-Card-Spend-Rules.md Outdated
Comment thread docs/articles/new-expensify/expensify-card/Expensify-Card-Spend-Rules.md Outdated
@github-actions

github-actions Bot commented Jun 6, 2026

Copy link
Copy Markdown
Contributor

HelpDot Documentation Review

Overall Assessment

This PR introduces a well-structured new article for Expensify Card Spend Rules and adds cross-references to four existing card articles. The new article covers a clear single workflow (admin Spend Rule management) and follows governance structure closely. There are several issues that should be addressed before merge, including a typo, heading compliance gaps, a full URL that should be relative, and minor formatting errors.

Scores Summary

  • Readability: 8/10 - Content is clear, steps are sequential and action-oriented, and the article is well-organized. Minor issues: a typo ("hpw" instead of "how"), double periods in two places, and a trailing space reduce polish.
  • AI Readiness: 7/10 - The new article has strong YAML metadata with proper internalScope, keywords, and description. Multiple "How to" headings support retrieval. However, two new # headings added to existing articles ("View Spend Rules on Your Card" and "Understand Spend Rule Decline Notifications") are not task-based -- they lack action verbs or question words. The troubleshooting subsection heading "Transaction declined by a Spend Rule" is also noun-based rather than task-based.
  • Style Compliance: 7/10 - Most UI elements are correctly bolded, cross-links use descriptive anchor text, and navigation instructions follow conventions. However, one cross-link uses a full URL instead of a relative link (governance requires relative links only), one instance of Save is missing bold formatting in a step, and the "View Spend Rules" heading does not follow the "How to" pattern required by governance.

Key Findings

Issues to address:

  • Typo in Cardholder-Settings-and-Features.md: "Learn hpw to set up" should be "Learn how to set up"
  • Full URL used in Cardholder-Settings-and-Features.md FAQ decline reasons: https://help.expensify.com/articles/new-expensify/expensify-card/Expensify-Card-Spend-Rules should be a relative link /articles/new-expensify/expensify-card/Expensify-Card-Spend-Rules
  • Double period and trailing space in Expensify-Card-Spend-Rules.md: "before any Spend Rule.. " (line in the default protections section)
  • Double period in Expensify-Card-Spend-Rules.md: "within the maximum amount.." (in the Allow mode evaluation description)
  • Missing bold on Save in the "How to edit or delete" section step 4: "Click Save" should be "Click Save"
  • Heading "# View Spend Rules on Your Card" (Cardholder-Settings-and-Features.md) should be task-based, e.g., "# How to view Spend Rules on your Expensify Card"
  • Heading "# Understand Spend Rule Decline Notifications" (Expensify-Card-Notifications.md) should be task-based, e.g., "# How to understand Spend Rule decline notifications"
  • Heading "## Transaction declined by a Spend Rule" (Troubleshoot-Expensify-Card-issues.md) is noun-based. Per governance, it should be action or question-based, e.g., "## What to do when a transaction is declined by a Spend Rule"
  • Minor grammar: "Blocking specific a merchant" should be "Blocking a specific merchant" in the Block rule examples

Positive aspects:

  • The new article's YAML frontmatter is thorough with a clear internalScope, relevant keywords, and a descriptive title
  • Cross-links use descriptive anchor text ("Learn how to..." / "Learn about...") per governance standards
  • The new article cleanly separates Block and Allow workflows with clear step instructions
  • FAQ section is well-structured with practical, user-relevant questions
  • Screenshot placeholders use the correct HTML comment format
  • Navigation instructions correctly follow the platform convention pattern ("on the left on web, on the bottom on mobile")
  • Existing link formats were improved from full URLs to relative links in several places (good cleanup)

Recommendations

  1. Fix the typo ("hpw" to "how") -- this is visible to users and easy to fix
  2. Convert the remaining full URL to a relative link in the FAQ decline reason bullet
  3. Fix double periods in the Spend Rules article (two occurrences)
  4. Bold "Save" in the edit/delete section step 4
  5. Revise non-task-based headings to start with action verbs or question words per governance. Note: the existing articles already use multiple # headings as an established pattern; the governance concern here is about making those headings task-based, not necessarily demoting them
  6. Fix "specific a merchant" grammar error

Files Reviewed

  • docs/articles/new-expensify/expensify-card/Expensify-Card-Spend-Rules.md (new) - Strong new article; needs minor punctuation and grammar fixes
  • docs/articles/new-expensify/expensify-card/Cardholder-Settings-and-Features.md (modified) - Typo, heading compliance, and one full URL need fixing
  • docs/articles/new-expensify/expensify-card/Expensify-Card-Notifications.md (modified) - Heading should be task-based
  • docs/articles/new-expensify/expensify-card/Set-Up-and-Manage-the-Expensify-Card.md (modified) - Cross-links are well-placed and properly formatted
  • docs/articles/new-expensify/expensify-card/Troubleshoot-Expensify-Card-issues.md (modified) - Heading should be task-based; content is clear and useful

Note: This review assessed only the proposed changes (diff), not unchanged portions of the files.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d012537df9

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

@stephanieelliott stephanieelliott added the HelpDot Apply this label if the issue relates to ExpensifyHelp label Jun 6, 2026
@stephanieelliott

Copy link
Copy Markdown
Contributor

Build for testing: https://92681.pr-testing.expensify.com/

stephanieelliott and others added 2 commits June 11, 2026 20:38
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@OSBotify

This comment has been minimized.

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@stephanieelliott stephanieelliott changed the title [No QA] [Hold for feature] Update help docs for Releases 1-4: Expensify Card Spend Rules [No QA] [Ready - Hold for feature] Update help docs for Releases 1-4: Expensify Card Spend Rules Jun 12, 2026
Co-authored-by: Stephanie Elliott <stephanieelliott@users.noreply.github.com>
@OSBotify

This comment has been minimized.

@MelvinBot

Copy link
Copy Markdown
Contributor Author

Fixed the failing Spell check — it was the only non-checklist check that failed.

Cause: a typo Expensif Card (missing the y) in the new article at Expensify-Card-Spend-Rules.md:128. cspell flagged Expensif as an unknown word.

Fix: corrected it to Expensify Card. Re-ran npm run spell-changed locally on the file — 0 issues. Pushed as a5e60c3.

@stephanieelliott stephanieelliott changed the title [No QA] [Ready - Hold for feature] Update help docs for Releases 1-4: Expensify Card Spend Rules [No QA] Update help docs for Releases 1-4: Expensify Card Spend Rules Jun 13, 2026
@stephanieelliott stephanieelliott requested a review from a team June 13, 2026 00:07
@melvin-bot

melvin-bot Bot commented Jun 13, 2026

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

@melvin-bot melvin-bot Bot requested review from lschurr and removed request for a team June 13, 2026 00:08
@melvin-bot

melvin-bot Bot commented Jun 13, 2026

Copy link
Copy Markdown

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

@clarajones-expensify clarajones-expensify merged commit 847d9a8 into main Jun 13, 2026
14 checks passed
@clarajones-expensify clarajones-expensify deleted the claude-ecardSpendRulesHelpDocs branch June 13, 2026 00:10
@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/clarajones-expensify in version: 9.4.8-0 🚀

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

Bundle Size Analysis (Sentry):

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/clarajones-expensify in version: 9.4.8-0 🚀

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

Bundle Size Analysis (Sentry):

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/puneetlath in version: 9.4.8-3 🚀

platform result
🕸 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

HelpDot Apply this label if the issue relates to ExpensifyHelp

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants