Skip to content

[Due for payment 2026-11-19] Promote the new Approve-only and Guest workspace roles on the Members page and role selector #105802

Open

Description

@JmillsExpensify

Background

We're adding two scoped workspace roles, Approve-only and Guest. Today an admin only finds them by opening the role selector for a specific member, so it's easy to not realize they exist. so most admins

We want admins to learn about the new roles where they already assign roles, without adding another pop-up or modal. We also want to hear which other scoped roles customers need.

This issue adds a New roles badge to the Members item in the workspace menu, a promo banner to the top of the Members page, and a grouped, annotated role selector with New badges and a feedback link. It changes how roles are presented only; no role's permissions change.

Product and design details

Applicability

We show every element in this issue to workspace admins who can change other members' roles, on any workspace where Approve-only and Guest can be assigned. Admins who can't change roles see none of it.

Members item in the workspace menu

Workspace menu with New roles badge on Members

Image
  • We add a New roles badge to the right of Members in the workspace menu (LHN on wide layouts, the workspace menu list on narrow layouts).
  • The badge reads New roles, not New, so admins don't read it as "new members."
  • We reuse the existing badge component used elsewhere in the LHN; no new component.
  • The badge hides once the admin dismisses the banner below. See Dismissal.

Banner on the Members page

Members page with default promo banner

Image
  • We add a banner at the top of the Members page, above Total workspace members.
  • We reuse the existing default promo banner (icon, title, supporting copy, close button); no new banner style.
  • Title: New roles available
  • Supporting copy: Give members just the access they need with new Approve-only and Guest roles., with Approve-only and Guest in bold.
  • Clicking the × dismisses the banner. See Dismissal.
  • We don't add a badge or tooltip to the Role column header.

Role selector RHP

Role RHP, grouped and alphabetical

Image

Header copy, above the list:

  • Assign a role to manage a member's workspace permissions. Compare workspace roles.
  • Compare workspace roles is a link that opens Managing Workspace Members in a new tab.

The list is split into two groups, each with a small group label, and a divider between them. Within each group, roles are in alphabetical order:

  1. Admin roles
    • Card admin: Manage workspace cards
    • Payments admin: Manage workflow payments
    • People admin: Manage members and approval workflows
    • Workspace admin: Manage reports and workspace settings
  2. Other roles
    • Approve-only with a New badge: Approve reports only
    • Auditor: View and comment on reports
    • Guest with a New badge: Submit reports with limited visibility
    • Member: Submit and approve reports

Footer, centered above Save:

  • Not seeing the role you need? Let us know.
  • Let us know opens a Concierge chat so the admin can describe the role they need.

The grouping, order, and header copy are permanent. Only the New badges are temporary.

Dismissal

  • Dismissing the banner is saved per admin, not per workspace, so an admin with several workspaces dismisses it once.
  • When the admin dismisses the banner, the New roles badge on Members also hides.
  • The New badges in the role selector stay until the promotion ends, independent of the banner.
  • We stop showing the banner, the New roles badge, and the New role badges for everyone 90 days after the roles launch.
Issue OwnerCurrent Issue Owner: @Krishna2323

Activity

  1. added
    ImprovementItem broken or needs improvement.
    InternalRequires API changes or must be handled by Expensify staff
    on Nov 3, 2026
  2. JmillsExpensify commented on Nov 3, 2026

    @JmillsExpensify
    ContributorAuthor

    @JS00001 any feedback on this dismissal logic? Maybe it's not worth it, and we just show thisfor 60 days and then remove it. Could be a more simple approach?

  3. JS00001 commented on Nov 3, 2026

    @JS00001
    Contributor

    @JmillsExpensify I see a few approaches we could take here:

    1. We should definitely add an NVP for dismissal, where the user can dismiss the banner/badge at any time
    2. As for the 60-90 day lifespan of this appearing, we could probably take two different approaches:
    • We just create the badges, and then in 90 days, merge a PR to remove the badges
    • We add some date-specific code in e/app to hide the banner after a certain time, and then we put up a PR to remove all of the code at any point in the future

    Tbh it seems simpler to have krishna create the badges, and then create a PR to remove the badges at the same time. Then in roughly 90 days, we can merge the follow up PR to remove the badges

  4. JmillsExpensify commented on Nov 3, 2026

    @JmillsExpensify
    ContributorAuthor

    That's cool with me. I can create an issue to remove them in that timeframe. Down to simplify.

  5. JS00001 commented on Nov 3, 2026

    @JS00001
    Contributor

    Sounds good, I have a Pr to add the nvp, @Krishna2323 it'll be for DismissProductTraining with name newWorkspaceRolesBanner

  6. JmillsExpensify commented on Nov 3, 2026

    @JmillsExpensify
    ContributorAuthor

    Thanks. Added @daledah for any reviews as well

  7. 2 remaining items

  8. stephanieelliott commented on Nov 6, 2026

    @stephanieelliott
    Contributor

    👋 sorry for the late add, but @daledah can we update the compare workspace roles link to use this instead: https://help.expensify.com/articles/new-expensify/workspaces/Understand-Workspace-Roles-and-Permissions

    Note that the URL is not live yet, but it will be as soon as this is merged #106171

  9. daledah commented on Nov 6, 2026

    @daledah
    Contributor

    @Krishna2323 could you please check this comment?

  10. shawnborton commented on Nov 6, 2026

    @shawnborton
    Contributor
  11. Krishna2323 commented on Nov 10, 2026

    @Krishna2323
    Contributor

    PR is merged!

  12. melvin-bot commented on Nov 11, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  13. Chandkia24 commented on Nov 11, 2026

    @Chandkia24

    Deploy Blocker #106589 was identified to be related to the PR #106052 that attempted to fix this issue.

  14. daledah commented on Nov 11, 2026

    @daledah
    Contributor

    Deploy Blocker #106589 was identified to be related to the PR #106052 that attempted to fix this issue.

    The App shipped the comparison link before its destination article was published. The documentation PR remains open and unmerged.

    not a blocker because the documentation PR remains open and unmerged

  15. jponikarchuk commented on Nov 11, 2026

    @jponikarchuk

    Deploy Blocker #106606 was identified to be related to the PR #106052 that attempted to fix this issue.

  16. stephanieelliott commented on Nov 11, 2026

    @stephanieelliott
    Contributor

    Cross-posting from Slack -- no need to block on this, it's being addressed here: https://expensify.slack.com/archives/C01GTK53T8Q/p1794427377024229?thread_ts=1794362359.913849&cid=C01GTK53T8Q

  17. changed the title [-]Promote the new `Approve-only` and `Guest` workspace roles on the `Members` page and role selector[/-] [+][Due for payment 2026-11-19] Promote the new `Approve-only` and `Guest` workspace roles on the `Members` page and role selector[/+] on Nov 12, 2026
  18. melvin-bot commented on Nov 12, 2026

    @melvin-bot

    @Krishna2323 / @daledah

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.36-0 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2026-11-19. 🎊

    The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

DailyKSv2ImprovementItem broken or needs improvement.InternalRequires API changes or must be handled by Expensify staff

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions