Skip to content

[Hold on feature] Docs updates for E/A#102933 Add Approve-only role to workspace members article - #104886

Merged
stephanieelliott merged 1 commit into
mainfrom
claude-docsApproveOnlyRole
Oct 27, 2026
Merged

stephanieelliott merged 1 commit into
mainfrom
claude-docsApproveOnlyRole

Conversation

@MelvinBot

@MelvinBot MelvinBot commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

Explanation of Change

[Payment due @Pujan92] Add approve-only workspace role added a new Approve-only workspace role on Control workspaces. People admins can assign it, and it appears as a role filter on the Members page. This PR updates Managing Workspace Members in New Expensify.

New feature: the Approve-only role. It's added to the role list and the role filter list.

Sentences that are now incorrect: People admins can now invite, remove, and assign Approve-only members, so these sentences are now wrong:

People admins can add and remove Members, Guests, and Auditors only, and cannot add or remove admins or other scoped admin roles.

People admins can only invite members as Members, Guests, or Auditors — they cannot assign admin roles.

People admins can only remove Members, Guests, and Auditors — they cannot remove admins or other scoped admin roles.

People admins can change a member’s role between Member, Guest, and Auditor only.

Each sentence now includes Approve-only. The role and filter labels were checked against the live web UI.

Live UI verification (web)

Role list: Workspace admin, Auditor, Guest, Card admin, People admin, Payments admin, Member, Approve-only ("Approve reports only.")

Role list showing Approve-only

Role filters: Workspace Admins, Approvers, Card Admins, People Admins, Payments Admins, Auditors, Guests, Approve-only, Members

Members role filters

@ShridharGoel, please review the files changed and confirm they reflect the current behavior. Then post a new comment saying @MelvinBot mark this PR as ready for review.

Fixed Issues

$ #102933
PROPOSAL:

Tests

// TODO: The human co-author must fill out the tests you ran before marking this PR as "ready for review"
// Please describe what tests you performed that validates your changed worked.

  • Verify that no errors appear in the JS console

Offline tests

QA Steps

// TODO: The human co-author must fill out the QA tests you ran before marking this PR as "ready for review".
// Please describe what QA needs to do to validate your changes and what areas do they need to test for regressions.

  • Verify that no errors appear in the JS console

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 verified any copy / text that was added to the app 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)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • 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)
  • 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 the PR adds or modifies the UI:
    • I asked an AI agent to review the changes for accessibility issues and addressed its findings.
    • I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
    • I verified all new/changed elements have meaningful accessible names and roles.
    • I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
  • 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
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari

Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>
@MelvinBot
MelvinBot requested a review from a team October 23, 2026 17:22
@MelvinBot MelvinBot added the HelpDot Apply this label if the issue relates to ExpensifyHelp label Oct 23, 2026
@ShridharGoel

Copy link
Copy Markdown
Contributor

@MelvinBot Mark this as ready

@MelvinBot
MelvinBot marked this pull request as ready for review October 24, 2026 20:15
@MelvinBot

Copy link
Copy Markdown
Contributor Author

🤖 This PR is now marked as ready for review.


view run

@melvin-bot

melvin-bot Bot commented Oct 24, 2026

Copy link
Copy Markdown

Product 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?

cc @dylanexpensify

@melvin-bot
melvin-bot Bot requested review from dylanexpensify and removed request for a team October 24, 2026 20:15
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 24, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-24T20:18:01.480198Z 324cd69 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@melvin-bot

melvin-bot Bot commented Oct 24, 2026

Copy link
Copy Markdown

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

- **Workspace admin** – Can manage members, roles, workflows, and settings.
- **Card admin** – Can manage the Expensify Card and Company cards, including issuing cards, setting limits, and assigning company cards. Has read-only access to Overview and Members, and all other workspace settings pages are hidden. (Control workspaces only)
- **People admin** – Can manage workspace membership and configure approval workflows. People admins can add and remove Members, Guests, and Auditors only, and cannot add or remove admins or other scoped admin roles. They have read-only access to the workspace overview and edit access to Members and the Approvals section of Workflows. All other workspace editor pages are hidden. (Control workspaces only)
- **People admin** – Can manage workspace membership and configure approval workflows. People admins can add and remove Members, Guests, Auditors, and Approve-only members only, and cannot add or remove admins or other scoped admin roles. They have read-only access to the workspace overview and edit access to Members and the Approvals section of Workflows. All other workspace editor pages are hidden. (Control workspaces only)

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.

Readability: "Auditors, and Approve-only members only" places "members only" directly after the "Approve-only" label, which reads ambiguously (as if "Approve-only members only" were one phrase). Reword for clarity, e.g. "...can only add and remove Members, Guests, Auditors, and Approve-only members, and cannot add or remove admins or other scoped admin roles."

@github-actions

Copy link
Copy Markdown
Contributor

HelpDot Documentation Review

Overall Assessment

This PR makes a small, focused update to Managing Workspace Members in New Expensify (/articles/new-expensify/workspaces/Managing-Workspace-Members) to document the new Approve-only workspace role on Control workspaces (+7 / -5). The changes add the role to the keyword list, add a new role definition bullet, add it to the role filter list, and correct four People admin permission sentences that were previously inaccurate. The additions are accurate, consistent, and verified against the live web UI.

Scores Summary

  • Readability: 9/10 - New bullet and sentence edits are concise and parallel in structure with the surrounding list items; the role definition clearly states the capability and its limitation.
  • AI Readiness: 8/10 - approve-only was correctly added to keywords, and the full feature name Approve-only is used consistently. No heading or hierarchy changes were needed for this content update.
  • Style Compliance: 9/10 - Role labels match the live UI exactly (confirmed in the PR UI verification), bolded consistently with existing role references, and the (Control workspaces only) qualifier follows the established pattern in the file.

Key Findings

  • Accurate correction of four previously incorrect sentences describing People admin invite/remove/role-change permissions, each now including Approve-only.
  • The new role bullet (Approve-only - Can approve reports but can't create expenses on the workspace. (Control workspaces only)) matches the pattern and tone of adjacent bullets.
  • Filter list entry added in the correct section with the standard phrasing.
  • Minor consistency note: keep the role ordering identical across the four permission sentences and the role/filter lists (Member, Guest, Auditor, Approve-only) for maximum scannability.
  • Out of scope for this diff: the article frontmatter has no internalScope field (pre-existing), so it is not penalized here, but it could be added in a future pass.

Recommendations

  • No blocking issues. The changes are ready pending the human co-author completing the Tests/QA sections of the PR template.
  • Optional: keep role ordering consistent across all four permission sentences and the role/filter lists for retrieval consistency.

Files Reviewed

  • docs/articles/new-expensify/workspaces/Managing-Workspace-Members.md - Approved. Accurate, well-formatted additions documenting the Approve-only role.

Note: This is an automated governance-based review. Scores are derived from docs/HELP_AUTHORING_GUIDELINES.md, docs/HELPSITE_NAMING_CONVENTIONS.md, and docs/TEMPLATE.md.

@stephanieelliott stephanieelliott changed the title Docs updates for E/A#102933 Add Approve-only role to workspace members article [Hold on feature] Docs updates for E/A#102933 Add Approve-only role to workspace members article Oct 26, 2026
@stephanieelliott

Copy link
Copy Markdown
Contributor

Moving this to Hold since we're hiding the ability to assign this role until blockers are resolved (see #102933 (comment))

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

looks good

@stephanieelliott
stephanieelliott merged commit 1497669 into main Oct 27, 2026
23 of 26 checks passed
@stephanieelliott
stephanieelliott deleted the claude-docsApproveOnlyRole branch October 27, 2026 21:44
@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/stephanieelliott in version: 9.5.24-1 🚀

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

@m-natarajan

m-natarajan commented Oct 27, 2026 •

Copy link
Copy Markdown

@ShridharGoel No QA steps, OK to checkoff?

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.

6 participants