Skip to content

[No QA] Docs updates for E/A#95729 Lowercase workspace role labels#95847

Open
MelvinBot wants to merge 3 commits into
mainfrom
docs-lowercase-role-titles-95729
Open

[No QA] Docs updates for E/A#95729 Lowercase workspace role labels#95847
MelvinBot wants to merge 3 commits into
mainfrom
docs-lowercase-role-titles-95729

Conversation

@MelvinBot

Copy link
Copy Markdown
Contributor

Explanation of Change

PR #95729 changed the workspace role labels shown in the app to sentence case in en.ts:

  • Workspace AdminWorkspace admin
  • Card AdminCard admin
  • People AdminPeople admin
  • Payments AdminPayments admin

This updates the canonical roles article Managing-Workspace-Members.md, where these appear as the exact UI role labels (the role-definition list, the role filter options, and the change-role notes), so the help site matches the current UI capitalization per docs/HELPSITE_NAMING_CONVENTIONS.md ("Use the exact text shown in the product UI. Match capitalization exactly.").

Scope note: Workspace Admin is used ~1,553 times across ~669 help-site files as a general persona/role reference in prose (e.g. "ask a Workspace Admin to…"). Those were intentionally left unchanged — they are editorial prose rather than direct UI-label references, and a site-wide sweep is a much larger, riskier change. If a broader normalization is desired, that should be scoped separately. Single-word labels (Owner, Auditor, Editor, Member) are unchanged since only the first word is capitalized in sentence case.

Fixed Issues

$ #95729

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.

QA

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


@jamesdeanexpensify, please review the files changed and confirm they reflect the current behavior. Then mark this PR Ready for review.

Co-authored-by: James Dean <jamesdeanexpensify@users.noreply.github.com>
@MelvinBot MelvinBot requested a review from a team July 10, 2026 16:26
@MelvinBot MelvinBot added the HelpDot Apply this label if the issue relates to ExpensifyHelp label Jul 10, 2026
NicolasBonet
NicolasBonet previously approved these changes Jul 10, 2026
@NicolasBonet

Copy link
Copy Markdown
Contributor

@MelvinBot please resolve conflicts

@MelvinBot

Copy link
Copy Markdown
Contributor Author

I looked into resolving the conflicts on this PR, but I can only make code changes (including merging main to resolve conflicts and pushing) when directed by the PR author, an assignee, or an existing co-author.

This PR's author/assignees are MelvinBot and jamesdeanexpensify, and the only human co-author is jamesdeanexpensifyNicolasBonet isn't on that list.

To have me resolve the conflicts, either:

  • Add NicolasBonet as an assignee on this PR and re-request, or
  • Have jamesdeanexpensify (assignee/co-author) reply tagging me to resolve conflicts.

@NicolasBonet

Copy link
Copy Markdown
Contributor

@jamesdeanexpensify please request it

@jamesdeanexpensify

Copy link
Copy Markdown
Contributor

@MelvinBot please resolve conflicts

…itles-95729

Co-authored-by: James Dean <jamesdeanexpensify@users.noreply.github.com>

# Conflicts:
#	docs/articles/new-expensify/workspaces/Managing-Workspace-Members.md
@MelvinBot

Copy link
Copy Markdown
Contributor Author

✅ Resolved the merge conflicts and pushed the merge of main — the PR is now mergeable.

The only conflict was in docs/articles/new-expensify/workspaces/Managing-Workspace-Members.md. main had meanwhile added a new Payments Admin role to the role-definition list and the role filter. I kept your sentence-case relabeling and carried that new role forward with the same convention (Payments AdminPayments admin, Payments AdminsPayments admins, and the mid-sentence "Payments Admin role" → "Payments admin role"), so nothing from main was dropped.

Please double-check the merged file and re-run any checks before marking it Ready for review.

@github-actions github-actions Bot changed the title Docs updates for E/A#95729 Lowercase workspace role labels [No QA] Docs updates for E/A#95729 Lowercase workspace role labels Jul 10, 2026
@OSBotify

This comment has been minimized.

@NicolasBonet NicolasBonet marked this pull request as ready for review July 10, 2026 18:56
@melvin-bot

melvin-bot Bot commented Jul 10, 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 @kadiealexander

@melvin-bot melvin-bot Bot requested a review from kadiealexander July 10, 2026 18:56
@melvin-bot

melvin-bot Bot commented Jul 10, 2026

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]

@melvin-bot melvin-bot Bot removed the request for review from a team July 10, 2026 18:56
- **Payments Admin** – Can manage workspace payment settings in the **Payments** section of **Workflows**, including business bank accounts, the authorized expense payer, and payment methods. Payment permissions are otherwise unchanged, so paying a report still depends on the relevant bank account being shared with the payer. Has read-only access to the workspace overview and Members, and all other workspace editor pages are hidden. (Control workspaces only)
- **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 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)

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.

Inconsistent capitalization: This line now lowercases the role label to "People admins", but standalone "Admins" ("cannot add or remove Admins or other scoped admin roles") remains title-cased. Per the Core UI Referencing Rules and the Deterministic Writing Rule ("Be consistent"), the same role term must use one consistent casing. Lowercase "admins" to match the updated role labels.

**Tip:** You can also invite members under **Settings > Profile** by clicking **Share** to send the workspace’s URL or QR code.

**Note:** Workspace Admins and People Admins can invite members. People Admins can only invite users as **Members** or **Auditors** — they cannot invite Admins or other scoped admin roles.
**Note:** Workspace admins and People admins can invite members. People admins can only invite users as **Members** or **Auditors** — they cannot invite Admins or other scoped admin roles.

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.

Inconsistent capitalization: You lowercased "Workspace admins" and "People admins" here, but "Admins" ("they cannot invite Admins or other scoped admin roles") is still title-cased on the same line. Per the Deterministic Writing Rule ("Be consistent") and exact-UI matching, use consistent casing — lowercase "admins".

- **Workspace Admins** – Shows only members with the Admin role (not available on Submit workspaces).
- **Card Admins** – Shows only members with the Card Admin role (Control workspaces only).
- **Payments Admins** – Shows only members with the Payments Admin role (Control workspaces only).
- **Workspace admins** – Shows only members with the Admin role (not available on Submit workspaces).

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.

Inconsistent capitalization: The filter label was lowercased to "Workspace admins", but the description still references "the Admin role" in title case. Per Core UI Referencing (match capitalization exactly) and the Deterministic Writing Rule, use the same casing for the role — lowercase "admin role".

If someone no longer needs access to your workspace, you can remove them individually or in bulk to keep your member list up to date.

**Note:** Workspace Admins and People Admins can remove members. People Admins can only remove **Members** and **Auditors** — they cannot remove Admins or other scoped admin roles.
**Note:** Workspace admins and People admins can remove members. People admins can only remove **Members** and **Auditors** — they cannot remove Admins or other scoped admin roles.

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.

Inconsistent capitalization: "Workspace admins" and "People admins" are lowercased here, but "Admins" ("they cannot remove Admins or other scoped admin roles") remains title-cased on the same line. Apply consistent lowercase casing per the Deterministic Writing Rule.

4. Select the new role and confirm.

**Note:** People Admins can change a member’s role between **Member** and **Auditor** only. Granting or removing the Admin role or any scoped admin role (such as Card Admin, People Admin, or Payments Admin) requires a Workspace Admin.
**Note:** People admins can change a member’s role between **Member** and **Auditor** only. Granting or removing the Admin role or any scoped admin role (such as Card admin, People admin, or Payments admin) requires a Workspace admin.

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.

Inconsistent capitalization: This line lowercases "Card admin, People admin, or Payments admin" and "Workspace admin", but leaves "the Admin role" title-cased. Per Core UI Referencing (match capitalization exactly) and the Deterministic Writing Rule ("Be consistent"), lowercase "admin role" to match the updated labels.

@github-actions

Copy link
Copy Markdown
Contributor

HelpDot Documentation Review

Overall Assessment

This is a small, focused PR (13 additions / 13 deletions) that normalizes workspace role labels in Managing-Workspace-Members.md from Title Case to sentence case (Workspace Admin to Workspace admin, Card Admin to Card admin, People Admin to People admin, Payments Admin to Payments admin) to match the UI label change made in PR 95729. The change is scoped to the canonical roles article where these strings function as exact UI-label references (the role-definition list, the role filter options, and the change-role notes).

Scores Summary

  • Readability: 9/10 - Purely cosmetic casing changes to existing well-formed prose and lists; clarity and flow are unaffected.
  • AI Readiness: 9/10 - Full feature/role names are preserved; changes do not touch headings, hierarchy, or metadata. Aligning labels to the live UI keeps semantic retrieval accurate against real search intent.
  • Style Compliance: 9/10 - Directly enforces HELPSITE_NAMING_CONVENTIONS.md: "Use the exact text shown in the product UI. Match capitalization exactly" and "Use Sentence case (match the UI exactly)." Bold formatting on labels is retained correctly.

Key Findings

  • Correctly targets only direct UI-label references (role definitions, the role filter menu options, and role-change notes), which is exactly where exact-capitalization rules apply.
  • The PR's scope note is sound: the ~1,553 general persona/prose uses of "Workspace Admin" across the help site were intentionally left unchanged, and a site-wide sweep is appropriately deferred to a separately scoped change.
  • Minor residual inconsistency: within some edited lines, related label references still use Title Case, e.g. "Shows only members with the Admin role", "cannot add or remove Admins", and bold Auditors / Members / Editors. These read as persona/prose per the PR's own rationale, but if the corresponding UI labels are also sentence case they should eventually be normalized for full consistency.
  • No heading, metadata, structure, cross-linking, or FAQ rules are affected by this diff; all remain compliant.

Recommendations

  • Safe to merge as-is; it improves UI-label accuracy with low risk.
  • Follow-up (optional, separate PR): confirm the UI casing of the remaining bold role references in these same lines (Admin/Admins, Auditor/Auditors, Member/Members, Editor/Editors) and normalize the ones that are true UI labels, so the article is internally consistent.
  • Fill in the Tests/QA sections of the PR body before marking ready for review (currently placeholder TODOs).

Files Reviewed

  • docs/articles/new-expensify/workspaces/Managing-Workspace-Members.md - Compliant; casing correctly aligned to current UI per naming conventions.

Note: This is a top-level summary review based solely on the proposed diff.

@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: 383189fa6a

ℹ️ 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".

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

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +48 to +50
- **Workspace admins** – Shows only members with the Admin role (not available on Submit workspaces).
- **Card admins** – Shows only members with the Card admin role (Control workspaces only).
- **Payments admins** – Shows only members with the Payments admin role (Control workspaces only).

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Keep member filter labels matching the UI

In the workspace members role filter I checked src/components/Tables/WorkspaceMembersTable/index.tsx, which renders these options from workspace.people.admins, cardAdmins, and paymentsAdmins; those translations still resolve in src/languages/en.ts to Workspace Admins, Card Admins, and Payments Admins. Lowercasing the filter labels here makes the help article no longer match the actual dropdown text for that flow, which conflicts with the stated goal of documenting exact UI labels.

Useful? React with 👍 / 👎.

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

Many more changes are needed @jamesdeanexpensify, please ask Melvin to take care of them

@jamesdeanexpensify

Copy link
Copy Markdown
Contributor

@MelvinBot please implement the changes

Co-authored-by: James Dean <jamesdeanexpensify@users.noreply.github.com>
@MelvinBot

Copy link
Copy Markdown
Contributor Author

✅ Implemented the review's follow-up — normalized the residual Title-Case role references in Managing-Workspace-Members.md so the whole article is internally consistent with the sentence-case UI labels. Pushed as 9cf705f.

What changed (7 occurrences):

  • Bare Admins / Admin used as generic prose → lowercased to match the already-lowercase "scoped admin role(s)" in the same sentences: "cannot add or remove admins", "cannot add admins", "cannot invite admins", "cannot remove admins", "removing the admin role", and "transfer ownership to another admin".
  • Filter description "Shows only members with the Admin role" → "Shows only members with the Workspace admin role", to use the exact UI label and parallel the sibling filter rows ("Card admin role", "Payments admin role").

What I intentionally left capitalized: the exact single-word UI labels — Member/Members, Auditor/Auditors, Editor/Editors, Owner. These are already correct in sentence case (only the first word is capitalized), consistent with this PR's original scope note. Bare Admin/Admins is not an exact UI label (the labels are Workspace admin, Card admin, etc.), which is why those were the ones normalized.

Please give the preview a quick look and re-run checks before marking Ready for review.

Note: I couldn't run prettier locally in this environment (command approval blocked), but the edits are in-place word substitutions with no whitespace/structural changes, so markdown formatting is unaffected. CI's prettier check will confirm.

@OSBotify

Copy link
Copy Markdown
Contributor

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

Updated articles:

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.

5 participants