Skip to content

feat: [91243] add agent promotion banners to workspace#91251

Merged
yuwenmemon merged 21 commits into
mainfrom
feat/91243-add-agent-promotion-banners-to-workspace
May 26, 2026
Merged

feat: [91243] add agent promotion banners to workspace#91251
yuwenmemon merged 21 commits into
mainfrom
feat/91243-add-agent-promotion-banners-to-workspace

Conversation

@NicolasBonet
Copy link
Copy Markdown
Contributor

@NicolasBonet NicolasBonet commented May 20, 2026

Explanation of Change

Adds two promotional banners to let users know about the existence of agents for workflows and rules:

  • Don’t see the rule you need? Add an agent
    • This is under the rules section of the workspace
  • Automate approvals with agents
    • This is located under the workflow settings of the workspace

Both banners are dismissable

Fixed Issues

$ #91243
PROPOSAL:#91243

Tests

  1. Enable the customAgent beta on a test workspace.
  2. Go to Workspace > Workflows > Approvals — verify the "Automate approvals with agents" green banner appears at the top of the approvals section.
  3. Dismiss the banner, then sign out and sign back in and return to the same page — verify the banner does not reappear.
  4. Go to Workspace > Rules — verify the "Don't see the rule you need?" green banner appears above the individual expense rules section.
  5. Tap the banner CTA and verify it navigates to the Workspace Workflows section.
  6. Return to Rules, dismiss the banner, then sign out and sign back in and return to the same page — verify the banner does not reappear.
  7. Repeat all steps on a workspace where the customAgent beta is not enabled — verify neither banner appears.
  • Verify that no errors appear in the JS console

Offline tests

No special test required.

QA Steps

Same as tests

  • 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 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.
  • I verified that similar component doesn't exist in the codebase
  • I verified that all props are defined accurately and each prop has a /** comment above it */
  • I verified that each file is named correctly
  • I verified that each component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
  • I verified that the only data being stored in component state is data necessary for rendering and nothing else
  • In component if we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
  • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
  • I verified that component internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
  • I verified that all JSX used for rendering exists in the render method
  • I verified that each component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
Screen.Recording.2026-05-20.at.5.42.41.PM.mov

@OSBotify

This comment has been minimized.

@github-actions
Copy link
Copy Markdown
Contributor

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

@codecov
Copy link
Copy Markdown

codecov Bot commented May 20, 2026

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines Coverage Δ
src/CONST/index.ts 93.84% <ø> (ø)
...iption/CardSection/BillingBanner/BillingBanner.tsx 90.47% <100.00%> (+5.47%) ⬆️
src/styles/index.ts 57.51% <ø> (ø)
src/styles/variables.ts 100.00% <ø> (ø)
src/types/onyx/DismissedProductTraining.ts 0.00% <ø> (ø)
src/pages/workspace/rules/PolicyRulesPage.tsx 96.00% <83.33%> (+96.00%) ⬆️
...ges/workspace/workflows/WorkspaceWorkflowsPage.tsx 51.28% <83.33%> (+51.28%) ⬆️
src/components/AgentPromotionalBanner.tsx 93.33% <93.33%> (ø)
... and 26 files with indirect coverage changes

@github-actions

This comment has been minimized.

@NicolasBonet
Copy link
Copy Markdown
Contributor Author

NicolasBonet commented May 20, 2026

@Expensify/design could I get some feedback about this?

Workspace Banner

Now

I was thinking in removing the "Nuevo" (New) badge in mobile or moving it before the title, thoughts?

IMG_0543

Proposal

image

Rules Banner

Now

I am not so sure, maybe remove the "Pruebalo" (try it) button, and simply make the banner clickable?

image

Proposal

image

@dubielzyk-expensify
Copy link
Copy Markdown
Contributor

Ideally we'd place the new badge inline with the title and the button on the promo should fold below on mobile:

image

Are we reusing the same component we have elsewhere cause that folds nicely automatically I believe

@NicolasBonet
Copy link
Copy Markdown
Contributor Author

Ideally we'd place the new badge inline with the title and the button on the promo should fold below on mobile:

it’s the same component, will re check tomorrow and see if I missed something

@NicolasBonet NicolasBonet force-pushed the feat/91243-add-agent-promotion-banners-to-workspace branch from 9462865 to 78b0aba Compare May 21, 2026 14:08
@NicolasBonet
Copy link
Copy Markdown
Contributor Author

NicolasBonet commented May 21, 2026

@dubielzyk-expensify I was double checking and I wasn't able to find a perfect match for a component with all those things, do you remember where we could find one with a custom icon, close icon, CTA and such?

I checked with Claude as well, and found nothing, the closest is a Banner component not used a lot in the app and it's still quite different.

@shawnborton
Copy link
Copy Markdown
Contributor

@NicolasBonet can you check and see if we have a "free trial" banner anywhere in the code? I think something like that could be a good starting point?

@github-actions
Copy link
Copy Markdown
Contributor

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

@NicolasBonet
Copy link
Copy Markdown
Contributor Author

NicolasBonet commented May 21, 2026

can you check and see if we have a "free trial" banner anywhere in the code? I think something like that could be a good starting point?

@shawnborton This is what I was able to see, but it has no close icon and it's all defined inline in the component:

image

I ended up changing the code I had and create it a re-usable component for other Agent promotional banners:

image

@shawnborton
Copy link
Copy Markdown
Contributor

There should be a free trial banner that is shown in the Inbox, typically on the Concierge chat or the #admins room? We might not use it anymore, but I could have sworn we did for the time-based discount or something?

@shawnborton
Copy link
Copy Markdown
Contributor

This is what I could find from Figma, but not sure what happened in the product:
image

@NicolasBonet
Copy link
Copy Markdown
Contributor Author

NicolasBonet commented May 21, 2026

This is what I could find from Figma, but not sure what happened in the product:

Found it after changing some code:

image

But it's still not like the one I implemented, it's called BillingBanner and seems to be used only for subscription stuff with different usages and no close icon, I could try to make it work for our use-case in here, but could be more work than using the existing one, let me give it a try and get back to you!

@NicolasBonet
Copy link
Copy Markdown
Contributor Author

NicolasBonet commented May 21, 2026

So @shawnborton in theory we could, but we would need to indeed change a lot of things in that component to make it work, specially for the places where it's used and the containers, we would need to tweak it a lot and add a lot of styles and embed the title using components to make it match, it's really not an ideal component to use for this case, and we probably would need to rename it as well as it won't be anymore a billing thing.

PS: I found that the design doesn't work well with the badge been inline with the title, it works differently in mobile vs web, so looking into it.

@Expensify Expensify deleted a comment from github-actions Bot May 21, 2026
@github-actions
Copy link
Copy Markdown
Contributor

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

@github-actions

This comment has been minimized.

@shawnborton
Copy link
Copy Markdown
Contributor

Sounds good, feel free to build something new - ideally generic like we have it in Figma so we can use it in other places if needed. @dubielzyk-expensify can further direct you, but I think that's a good starting point!

@NicolasBonet NicolasBonet marked this pull request as ready for review May 21, 2026 20:04
@NicolasBonet NicolasBonet requested review from a team as code owners May 21, 2026 20:04
@melvin-bot melvin-bot Bot requested review from shubham1206agra and trjExpensify and removed request for a team May 21, 2026 20:04
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented May 21, 2026

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

@melvin-bot melvin-bot Bot removed the request for review from a team May 21, 2026 20:04
@shubham1206agra
Copy link
Copy Markdown
Contributor

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible 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 checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified there are no new alerts related to the canBeMissing param for useOnyx
  • I verified proper code patterns were followed (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
    • 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 verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • 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
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • 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
  • xIf 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 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.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this 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.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Screen.Recording.2026-05-26.at.12.20.05.AM.mov
Screen.Recording.2026-05-26.at.12.25.06.AM.mov
Screen.Recording.2026-05-26.at.12.34.50.AM.mov

@shubham1206agra
Copy link
Copy Markdown
Contributor

@NicolasBonet Please address everything discussed here

- Introduced new constants for AGENTS_WORKFLOWS_BANNER and AGENTS_RULES_BANNER in CONST.
- Updated AgentPromotionalBanner component to require Sentry labels for CTA.
- Refactored PolicyRulesPage and WorkspaceWorkflowsPage to use new constants for Sentry labels.
- Adjusted the margin of the badge in the AgentPromotionalBanner component for improved spacing.
- Removed unnecessary whitespace in the title rendering for cleaner output.
- Changed button size from large to medium for better UI consistency.
@NicolasBonet
Copy link
Copy Markdown
Contributor Author

@shubham1206agra @shawnborton replied and fixed

The button looks bigger than expected. NAB though

That is not the resolution you have in figma, it will expand until the next breaking point.

Looks like we want the 40px "medium"/"normal" button, according to Figma:

Done

@yuwenmemon
Copy link
Copy Markdown
Contributor

@shubham1206agra this should be good for another review

@shubham1206agra
Copy link
Copy Markdown
Contributor

Screenshot 2026-05-26 at 7 08 16 AM

@NicolasBonet Spacing is missing in native device

@github-actions
Copy link
Copy Markdown
Contributor

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

@github-actions
Copy link
Copy Markdown
Contributor

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

@Expensify Expensify deleted a comment from github-actions Bot May 26, 2026
@github-actions

This comment has been minimized.

@NicolasBonet
Copy link
Copy Markdown
Contributor Author

NicolasBonet commented May 26, 2026

Fixed in all platforms:

Screen.Recording.2026-05-26.at.9.50.39.AM.mov
Screen.Recording.2026-05-26.at.10.05.04.AM.mov
Screen.Recording.2026-05-26.at.10.03.07.AM.mov


const hasCta = !!ctaText && !!onCtaPress;

const titleNode = useMemo(
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.

❌ CLEAN-REACT-PATTERNS-0 (docs)

React Compiler is enabled in this codebase and automatically memoizes derived values. The useMemo wrapping titleNode (line 48) and rightComponent (line 66) is redundant — the compiler will handle caching these JSX expressions based on their captured dependencies.

Remove both useMemo calls and declare the values as plain expressions:

const titleNode = (
    <View style={[styles.flexRow, styles.flexShrink1]}>
        <Text style={[styles.textStrong]}>
            {title}
            <Badge ... />
        </Text>
    </View>
);

Similarly for rightComponent — use a plain conditional expression instead of useMemo. Also remove the useMemo import from react (line 1).

Note: If this file does not compile with React Compiler, the manual memoization may be necessary until the compilation issue is resolved — verify with npm run react-compiler-compliance-check check-changed.


Reviewed at: 75575dd | Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

@yuwenmemon yuwenmemon merged commit 20222e7 into main May 26, 2026
43 checks passed
@yuwenmemon yuwenmemon deleted the feat/91243-add-agent-promotion-banners-to-workspace branch May 26, 2026 20:46
@github-actions
Copy link
Copy Markdown
Contributor

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

@OSBotify
Copy link
Copy Markdown
Contributor

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

@dubielzyk-expensify
Copy link
Copy Markdown
Contributor

dubielzyk-expensify commented May 27, 2026

Just noticed that we're using the small button here:

CleanShot 2026-05-27 at 11 06 09@2x

Should be using the regular button according to the mocks:

CleanShot 2026-05-27 at 11 06 30@2x

The text underneath should also be label and not our regular body size.

Lastly we should tighten up the spacing around the button and X button to be more inline with the mocks

@shubham1206agra
Copy link
Copy Markdown
Contributor

@MelvinBot Can you create a follow up PR for addressing #91251 (comment)?

@MelvinBot
Copy link
Copy Markdown
Contributor

🤖 Follow-up PR created: #91795

Addresses the design feedback from dubielzyk-expensify:

  • Button size changed from small → medium (regular) on wide layout
  • Subtitle text uses label font size instead of body size
  • Gap spacing tightened from 16px → 12px

Please mark it as "Ready for review" when it is ready for review.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants