[No QA] [Payment due @dukenv0307] [No QA] Add Playroll integration help page

[MelvinBot]

Explanation of Change

Adds a new help page for the Playroll HR/EOR integration under Expensify Classic connections. The page documents the full setup process including prerequisites, enabling Public Receipt Visibility, setting Receipt Required Amount to $0, connecting via Partner credentials in Playroll, and mapping expense categories. This is a one-way integration (Expensify → Playroll) for syncing approved expenses.

Fixed Issues

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

Tests

N/A — docs-only change (help page update). No functional code changes.

Offline tests

N/A — docs-only change

QA Steps

N/A — docs-only change. Verify the help page renders correctly via the preview link.

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I followed proper code patterns (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
  • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
• I verified that if a function's arguments changed that all usages have also been updated correctly
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
• If new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

N/A — docs-only change

Android: mWeb Chrome

N/A — docs-only change

iOS: Native

N/A — docs-only change

iOS: mWeb Safari

N/A — docs-only change

MacOS: Chrome / Safari

N/A — docs-only change

[NickTooker]

How TO: Expensify → Playroll Expense Integration Setup
Purpose:
 This integration allows approved expenses in Expensify to automatically sync into Playroll for processing.
Important:

This is a one-way integration (Expensify → Playroll only)
Changes made after syncing will not sync back
Only approved expenses sync
Expenses without receipts will not sync
Prerequisites:

User must be a Workspace Admin or Workspace Owner in Expensify
User must have Playroll integration permissions
User must be logged into the same Expensify account that owns/administers the workspace
User must be able to access Expensify Classic
Setup Steps:

1. Switch to Expensify Classic

Log into Expensify
Click account logo
Select “Troubleshoot”
Click “Switch to Expensify Classic”
2. Enable Public Receipt Visibility

Go to Settings → Workspaces
Select the workspace
Go to Rules
Enable “Public Receipt Visibility”
Important:
 If this is not enabled, expenses will not sync to Playroll.
3. Set Receipt Required Amount to 0

In Rules section
Locate “Receipt Required Amount”
Set value to 0
Save changes
Reason:
 Expenses without receipts do not sync to Playroll.
4. Confirm Workspace Permissions
 The user configuring the integration must be:

Workspace Admin OR
Workspace Owner
5. Connect Expensify to Playroll
 In Playroll:

Go to Dashboard
Click Tools → Integrations
Select Expensify
Open Configuration tab
Click Connect
You will need:

Partner User ID
Partner User Secret
To get credentials:

While logged into Expensify, click “Find our Partner ID”
Copy Partner User ID and Partner User Secret
Paste into Playroll
Click Submit
Successful setup will show:
 “Active / Connected”
6. Map Expense Categories

Open Expensify integration page
Go to Expense Categories
Click “Map Categories”
Match Expensify categories to Playroll categories
Save mappings
Examples:

Expensify “Car” → Playroll “Car Rental”
Expensify “Equipment” → Playroll “Equipment”
Important:
 Employee email addresses in Expensify must match Personal Emails in Playroll.
Completion Checklist:

Public Receipt Visibility enabled
Receipt Required Amount set to 0
Correct workspace permissions confirmed
Expensify connected to Playroll
Expense categories mapped and saved

[MelvinBot]

Fixed the failing spellcheck: added "Playroll" to the cspell dictionary (cspell.json).

[OSBotify]

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

Updated articles:

• articles/expensify-classic/connections/Playroll

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

[melvin-bot]

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

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR adds a new Expensify Classic integration article for Playroll, covering setup steps to connect Expensify with Playroll for expense syncing. The article is procedurally clear and covers a single workflow, but it has several structural violations of the HelpDot governance rules that need to be addressed before merging.

Scores Summary

• Readability: 7/10 - Steps are clear and sequential with good use of callouts, but the "Step N:" heading pattern adds noise, and the Completion Checklist section at the end is unconventional for HelpDot articles.
• AI Readiness: 3/10 - Missing required internalScope in YAML frontmatter. Multiple # headings violate the single-#-heading rule. No task-based headings with action verbs or question words for content sections. No "How to" heading present anywhere in the article.
• Style Compliance: 5/10 - Button and tab names are properly bolded. However, category names in the example section are wrapped in quotation marks (prohibited). Several headings use forbidden generic terms ("Prerequisites," "Setup Steps," "Step 1," "Step 2," etc.).

Key Findings

Critical issues that must be addressed:

1. Missing internalScope metadata -- The YAML frontmatter is missing the required internalScope field. Per HELP_AUTHORING_GUIDELINES.md Section 3 and TEMPLATE.md, every article must include internalScope defining audience, covered workflow, and explicit exclusions.

2. Multiple # headings -- The article uses # Prerequisites, # Setup Steps, and # Completion Checklist in addition to the implied article title. The governance rules mandate exactly one # heading (the article title), with # FAQ as the only exception. All other sections must use ##.

3. Forbidden generic headings -- "Prerequisites," "Setup Steps," "Completion Checklist," and all "Step N:" headings are explicitly forbidden. The rules prohibit "Setup," "Step 1," and any noun-only or topic-only headings. Every heading must be task-based, starting with an action verb or question word.

4. No "How to" heading -- HELP_AUTHORING_GUIDELINES.md Section 6 and the validation checklist require at least one "How to..." heading using the feature name. None exists in this article.

Additional issues:

5. Quotation marks around category names -- The example section uses "Car", "Car Rental", "Equipment" in quotation marks. Per HELPSITE_NAMING_CONVENTIONS.md, UI element names and labels should not be wrapped in quotation marks; use bold formatting instead.

6. Heading restructuring needed -- All ## Step N: headings should be converted to task-based ## headings. For example:

   • ## Step 1: Switch to Expensify Classic should become ## How to switch to Expensify Classic
   • ## Step 2: Enable Public Receipt Visibility should become ## How to enable Public Receipt Visibility
   • ## Step 5: Connect Expensify to Playroll should become ## How to connect Expensify to Playroll
   • ## Step 6: Map Expense Categories should become ## How to map expense categories in Playroll

7. Article title heading -- The article lacks an explicit # title heading in the body. Per the template, there should be exactly one # heading matching the article title, followed by a brief explanation of the feature.

Positive aspects:

• The article covers a single, well-defined workflow (connecting Expensify to Playroll).
• Steps are sequential, clear, and action-oriented with good procedural flow.
• Callout blocks ({% include info.html %}) are used effectively to highlight important prerequisites and constraints.
• UI button and tab names are consistently bolded throughout the numbered steps.
• The description and keywords in the YAML metadata are well-crafted for search intent.
• The introductory paragraph clearly explains the integration scope and limitations (one-way sync, approved expenses only).

Recommendations

1. Add internalScope to YAML frontmatter. Suggested value: internalScope: Audience is Workspace Admins and Workspace Owners. Covers connecting Expensify Classic to Playroll for one-way expense syncing. Does not cover Playroll account setup, New Expensify integration, or two-way sync workflows.

2. Restructure headings to use exactly one # heading for the article title (e.g., # How to connect Expensify to Playroll), then convert all section headings to task-based ## headings with action verbs. Remove all "Step N:" prefixes.

3. Remove or restructure the # Prerequisites section. Consider renaming to ## Who can connect Expensify to Playroll (matching the template pattern) and demoting to ##.

4. Remove or restructure the # Completion Checklist section. This pattern is not part of the HelpDot template. If the information is valuable, incorporate it into a ## How to verify your Playroll connection section.

5. Replace quotation marks with bold formatting in the category mapping example (e.g., change "Car" to **Car**).

6. Ensure at least one heading includes "How to" with the feature name for AI retrieval optimization.

Files Reviewed

• docs/articles/expensify-classic/connections/Playroll.md -- New file; requires heading restructuring, missing metadata field, and formatting fixes as detailed above.
• cspell.json -- Adding "Playroll" to the dictionary; no issues.

This review is based on the HelpDot governance rules defined in docs/HELP_AUTHORING_GUIDELINES.md, docs/HELPSITE_NAMING_CONVENTIONS.md, and docs/TEMPLATE.md.

[dukenv0307]

@MelvinBot Please complete the checklist. We don't need the test cases in this PR since we just updated the help page

[melvin-bot]

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

[MelvinBot]

⚠️ Something went wrong. This may be a transient issue — try again. If it persists, check status.anthropic.com.

Run details

[stephanieelliott]

Applied all relevant bot comments.

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR adds a new Expensify Classic help article for the Playroll integration. The article is well-structured, follows governance conventions closely, and provides clear step-by-step instructions for connecting Expensify to Playroll. It covers a single workflow (connecting the integration) with appropriate supporting sections. The cspell.json change is a correct housekeeping addition.

Scores Summary

• Readability: 9/10 - Clear, scannable, and well-organized. The two-phase numbered step structure (Expensify setup then Playroll connection) is logical and easy to follow. Bullet lists in the FAQ and "What happens" section are concise.
• AI Readiness: 9/10 - YAML metadata is complete and well-targeted. All headings are task-based with the feature name included. The "How to" heading satisfies retrieval requirements. The internalScope field clearly defines audience and boundaries.
• Style Compliance: 8/10 - Navigation phrasing, button bolding, and mobile availability callout all follow conventions. A few minor items noted below.

Key Findings

• The article follows the template structure faithfully: ## Who can connect, ## How to connect, ## What happens after you connect, and # FAQ -- all matching governance expectations.
• Headings are all task-based or question-based with no forbidden generic headings. Heading hierarchy uses only # and ## as required.
• The internalScope metadata is well-written, clearly stating audience (Workspace Admins and Workspace Owners) and explicit exclusions (Playroll configuration beyond the integration).
• Navigation uses the correct "In the navigation tabs on the left" phrasing per HELPSITE_NAMING_CONVENTIONS.md.
• "This feature is not available on mobile." is stated clearly in the eligibility section, matching the required phrasing exactly.
• FAQ questions are in question format and cover realistic user concerns.

Recommendations

1. Step 6 ("Save your changes"): If there is a literal Save button in the UI, the button name should be bolded per Button Naming Standards (e.g., "Click Save."). Currently "Save your changes" reads as a general instruction rather than a specific UI action. Clarify whether there is an explicit button to click.
2. Trailing whitespace in H1: The # Playroll heading has a trailing space. This is cosmetic but worth cleaning up.
3. YAML title: The governance guidelines suggest a "Clear task-based title using feature name" (e.g., "Connect Expensify to Playroll"). The current title "Playroll" is acceptable for an integration reference article, but a task-based title would better align with authoring guidelines and improve search discoverability.
4. Consider bolding "Personal Email": In the note "Employee email addresses in Expensify must match the Personal Email addresses in Playroll," if "Personal Email" is a specific field label in Playroll's UI, it should be bolded per UI referencing rules.

Files Reviewed

• docs/articles/expensify-classic/connections/Playroll.md -- New file. Well-structured integration article with minor style refinements suggested above.
• cspell.json -- Added "Playroll" to the spell-check dictionary. Alphabetical placement is correct.

Review based on docs/HELPSITE_NAMING_CONVENTIONS.md, docs/HELP_AUTHORING_GUIDELINES.md, and docs/TEMPLATE.md governance standards.

[github-actions]

AI readiness / Metadata: The YAML title field should be a task-based title per HELP_AUTHORING_GUIDELINES.md Section 3 and TEMPLATE.md. A noun-only title like "Playroll" does not describe what the user will accomplish.

Suggested fix:

Suggested change

	---
	title: Connect Expensify to Playroll

[github-actions]

Heading rule violation: Per HELP_AUTHORING_GUIDELINES.md Section 2 and Section 4, the single # heading (article title) should not be a noun-only label. It must be task-based and match the YAML title. If the title is updated to be task-based (e.g., "Connect Expensify to Playroll"), this heading should match.

Suggested change

	# Connect Expensify to Playroll

[github-actions]

Naming and style: Per HELPSITE_NAMING_CONVENTIONS.md, button names must be bolded and use the exact UI label. "Save your changes" is vague -- if there is a specific button (e.g., Save), reference it with the exact label bolded and use an action verb like "Click". If no explicit save button exists, clarify what the user actually does.

Suggested fix:

Suggested change

	6. Click **Save**.

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR adds a new Expensify Classic help article for the Playroll integration, along with a cspell dictionary entry. The article is well-structured, follows a single-workflow focus (connecting Expensify to Playroll), and adheres to most governance conventions. It is a solid addition with only minor areas for improvement.

Scores Summary

• Readability: 9/10 - Clear, scannable, and well-organized. Steps are sequential and action-oriented. The two-phase connection process (Expensify settings first, then Playroll configuration) is logically separated with explanatory transitions.
• AI Readiness: 9/10 - Strong YAML metadata with descriptive internalScope, relevant keywords, and a clear description. All headings are task-based and include the feature name. Includes a "How to" heading as required. Heading hierarchy uses only # and ## correctly.
• Style Compliance: 8/10 - UI elements are bolded correctly throughout. FAQ questions are well-formed. Minor deviations noted below.

Key Findings

• The article correctly limits itself to one primary workflow (connecting Expensify to Playroll) and appropriately scopes out Playroll-side configuration in internalScope.
• All section headings are task-based and include the feature name, matching the authoring guidelines precisely.
• The FAQ section is well-structured with concise, direct answers to realistic user questions.
• The "This feature is not available on mobile" statement is correctly placed per governance rules.
• Minor: Step 1 uses "In the navigation tabs on the left, go to Settings > Workspaces." The governance convention for web navigation is "Use the navigation tabs on the left" as a standalone phrase. Consider aligning to the exact phrasing, e.g., splitting into "In the navigation tabs on the left, click Settings. Then select Workspaces." or similar to match the documented convention more precisely.
• Minor: Step 6 says "Save your changes." without bolding a specific button name. If there is a Save button in the UI, it should be bolded per button naming standards.
• Minor: The article has no cross-links, which is acceptable for a self-contained integration article, but if there is a related "workspace settings" or "receipt visibility" article, a link after the prerequisites section could help users who need more context on those settings.

Recommendations

1. Consider bolding "Save" in step 6 if it corresponds to a specific UI button (e.g., "Click Save.").
2. Review the navigation phrasing in step 1 against the naming conventions for web navigation to ensure exact alignment.
3. No blocking issues -- this article is ready for publication with these minor refinements.

Files Reviewed

• docs/articles/expensify-classic/connections/Playroll.md -- New article. Well-structured, governance-compliant, minor style refinements suggested.
• cspell.json -- Added "Playroll" to the dictionary. Correct and necessary.

Note: This review is based solely on the proposed changes in the PR diff, evaluated against the HelpDot governance files (HELPSITE_NAMING_CONVENTIONS.md, HELP_AUTHORING_GUIDELINES.md, and TEMPLATE.md).

[github-actions]

🚧 @kadiealexander has triggered a test Expensify/App build. You can view the workflow run here.

[github-actions]

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #90394.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-e3b5200-e48a63d-ade0d5c6a0ac9dd245d83d11bfc52a4652bd34c5/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-e3b5200-e48a63d-2c4ac848ed4e24355c7cb26bcf21781b2d160171/index.html

Web 🕸️
https://90394.pr-testing.expensify.com

---

👀 View the workflow run that generated this build 👀

[OSBotify]

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

[OSBotify]

🚀 Deployed to staging by https://github.com/kadiealexander in version: 9.3.76-0 🚀

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

[OSBotify]

🚀 Deployed to production by https://github.com/roryabraham in version: 9.3.77-3 🚀

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

[melvin-bot]

🤖 Payment issue created: #91124