Skip to content

[NoQA] Add Gusto approval mode settings#89653

Open
ShridharGoel wants to merge 13 commits intoExpensify:mainfrom
ShridharGoel:gusto1.8
Open

[NoQA] Add Gusto approval mode settings#89653
ShridharGoel wants to merge 13 commits intoExpensify:mainfrom
ShridharGoel:gusto1.8

Conversation

@ShridharGoel
Copy link
Copy Markdown
Contributor

@ShridharGoel ShridharGoel commented May 5, 2026

Explanation of Change

Adds the Gusto approval mode settings for the HR workspace page.

Fixed Issues

$ #87013
PROPOSAL:

Tests

  1. Enable Gusto beta (gustoNewDot).
  2. Go to workspace settings.
  3. Enable the HR option in more features.
  4. Go to the HR page.
  5. Connect Gusto if not connected.
  6. Verify that the "Approval mode" row is showing after the connection is successful.
  7. Click on the row.
  8. Verify that the options to change approval mode show.
  9. Change the mode.
  10. Save it.
  • Verify that no errors appear in the JS console

Offline tests

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.

Screenshots/Videos

Android: Native
Screen.Recording.2026-05-06.at.9.24.02.AM.mov
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
Screen.Recording.2026-05-06.at.9.25.11.AM.mov

@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented May 5, 2026

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

  1. Look at the code and make sure there are no malicious changes.
  2. Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx ts-node ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx ts-node ./scripts/generateTranslations.ts --compare-ref main

@codecov
Copy link
Copy Markdown

codecov Bot commented May 5, 2026

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines Coverage Δ
src/CONST/index.ts 92.30% <ø> (ø)
src/ROUTES.ts 17.28% <100.00%> (ø)
src/SCREENS.ts 100.00% <ø> (ø)
...gation/linkingConfig/RELATIONS/WORKSPACE_TO_RHP.ts 100.00% <ø> (ø)
src/libs/Navigation/linkingConfig/config.ts 76.92% <ø> (ø)
...gation/AppNavigator/ModalStackNavigators/index.tsx 6.75% <0.00%> (-0.01%) ⬇️
src/libs/actions/connections/Gusto.ts 0.00% <0.00%> (ø)
src/pages/workspace/hr/WorkspaceHRPage.tsx 0.00% <0.00%> (ø)
...pages/workspace/hr/gusto/GustoApprovalModePage.tsx 0.00% <0.00%> (ø)
... and 295 files with indirect coverage changes

@ShridharGoel ShridharGoel changed the title Add Gusto approval settings Add Gusto approval mode settings May 5, 2026
@ShridharGoel ShridharGoel changed the title Add Gusto approval mode settings [NoQA] Add Gusto approval mode settings May 6, 2026
@ShridharGoel ShridharGoel marked this pull request as ready for review May 6, 2026 03:56
@ShridharGoel ShridharGoel requested review from a team as code owners May 6, 2026 03:56
@melvin-bot melvin-bot Bot requested review from shubham1206agra and removed request for a team May 6, 2026 03:56
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented May 6, 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 requested review from JmillsExpensify and removed request for a team May 6, 2026 03:56
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

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: 0299513468

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread src/languages/es.ts Outdated
@ShridharGoel
Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector
Copy link
Copy Markdown

Codex Review: Didn't find any major issues. 🚀

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

@shubham1206agra
Copy link
Copy Markdown
Contributor

@yuwenmemon Please run polyglot parrot on this PR. Thanks.

Comment on lines +26 to +28
if (!policyID) {
return;
}
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.

@ShridharGoel NAB: But we don't need to check for undefined policies. Also, you can make the param policyID as string only.

@shubham1206agra
Copy link
Copy Markdown
Contributor

@Expensify/design Tagging here for design approval

@shubham1206agra
Copy link
Copy Markdown
Contributor

@yuwenmemon Changing approval mode is not working from BE side

{
    "jsonCode": 200,
    "requestID": "9f79a340eca674f6-DEL",
    "onyxData": [
        {
            "key": "policy_097D01B921724B07",
            "onyxMethod": "merge",
            "value": {
                "connections": {
                    "gusto": {
                        "config": {
                            "approvalMode": ""
                        }
                    }
                }
            }
        }
    ],
    "previousUpdateID": 13104054341,
    "lastUpdateID": 13104062395
}

@ShridharGoel
Copy link
Copy Markdown
Contributor Author

Changing approval mode is not working from BE side

That's known, @yuwenmemon has already handled it. Should be live soon.

@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-06.at.10.46.13.PM.mov

@OSBotify
Copy link
Copy Markdown
Contributor

OSBotify commented May 6, 2026

🦜 Polyglot Parrot! 🦜

Squawk! Looks like you added some shiny new English strings. Allow me to parrot them back to you in other tongues:

View the translation diff
diff --git a/src/languages/de.ts b/src/languages/de.ts
index 3f0f6f16..25b54343 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -7031,24 +7031,15 @@ Fügen Sie weitere Ausgabelimits hinzu, um den Cashflow Ihres Unternehmens zu sc
                 approvalMode: 'Genehmigungsmodus',
                 finalApprover: 'Endgültige:r Genehmiger:in',
                 notSet: 'Nicht festgelegt',
-                approvalModeDescription: 'Mitglieder und Vorgesetzte sind für die Synchronisierung mit Gusto eingerichtet.',
+                approvalModeDescription: 'Mitglieder und Manager sind für die Synchronisation mit Gusto eingerichtet.',
                 approvalModeWarningTitle: 'Genehmigungsmodus ändern?',
                 approvalModeWarningPrompt: (helpSiteURL: string) =>
-                    `Möchtest du den Genehmigungsmodus für diesen Arbeitsbereich wirklich ändern? Weitere Informationen zu den verschiedenen Gusto-gestützten Arbeitsablaufmodi findest du auf unserer <a href="${helpSiteURL}">Hilfeseite</a>.`,
+                    `Möchten Sie den Genehmigungsmodus für diesen Workspace wirklich ändern? Erfahren Sie mehr über die verschiedenen Gusto-aktivierten Workflow-Modi auf unserer <a href="${helpSiteURL}">Hilfeseite</a>.`,
                 approvalModeWarningConfirm: 'Genehmigungsmodus ändern',
                 approvalModes: {
-                    basic: {
-                        label: 'Einfache Genehmigung',
-                        description: 'Alle Benutzer reichen bei einer einzelnen Person zur Bearbeitung und Genehmigung ein.',
-                    },
-                    manager: {
-                        label: 'Genehmigung durch Vorgesetzte',
-                        description: 'Mitarbeitende reichen Berichte bei ihrem in Gusto konfigurierten direkten Vorgesetzten ein.',
-                    },
-                    custom: {
-                        label: 'Benutzerdefinierte Genehmigung',
-                        description: 'Ich richte Genehmigungsworkflows manuell in Expensify ein.',
-                    },
+                    basic: {label: 'Einfache Genehmigung', description: 'Alle Benutzer reichen zur Bearbeitung und Genehmigung bei einer einzigen Person ein.'},
+                    manager: {label: 'Managergenehmigung', description: 'Mitarbeitende reichen Berichte bei ihrer in Gusto hinterlegten direkten Führungskraft ein.'},
+                    custom: {label: 'Benutzerdefinierte Genehmigung', description: 'Ich richte Genehmigungs-Workflows in Expensify manuell ein.'},
                 },
                 connect: 'Verbinden',
                 connectionDescription: 'Verbinde Gusto, um Mitarbeitergenehmigungen mit deinem Workspace zu synchronisieren.',
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index be61d34e..f4173899 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -7054,23 +7054,14 @@ Ajoutez davantage de règles de dépenses pour protéger la trésorerie de l’e
                 finalApprover: 'Approbateur final',
                 notSet: 'Non défini',
                 approvalModeDescription: 'Les membres et les responsables sont configurés pour se synchroniser avec Gusto.',
-                approvalModeWarningTitle: 'Modifier le mode d’approbation ?',
+                approvalModeWarningTitle: 'Changer le mode d’approbation ?',
                 approvalModeWarningPrompt: (helpSiteURL: string) =>
-                    `Voulez-vous vraiment modifier le mode d’approbation de cet espace de travail ? En savoir plus sur les différents modes de flux de travail compatibles avec Gusto sur notre <a href="${helpSiteURL}">site d’aide</a>.`,
+                    `Êtes-vous sûr·e de vouloir modifier le mode d’approbation de cet espace de travail ? En savoir plus sur les différents modes de workflow compatibles avec Gusto sur notre <a href="${helpSiteURL}">site d’aide</a>.`,
                 approvalModeWarningConfirm: 'Modifier le mode d’approbation',
                 approvalModes: {
-                    basic: {
-                        label: 'Approbation simple',
-                        description: 'Tous les utilisateurs soumettent leurs rapports à une seule personne pour traitement et approbation.',
-                    },
-                    manager: {
-                        label: 'Approbation par responsable',
-                        description: 'Les employés soumettent leurs rapports à leur responsable direct configuré dans Gusto.',
-                    },
-                    custom: {
-                        label: 'Approbation personnalisée',
-                        description: 'Je configurerai manuellement les flux de travail d’approbation dans Expensify.',
-                    },
+                    basic: {label: 'Approbation simple', description: 'Tous les utilisateurs soumettent à une seule personne pour traitement et approbation.'},
+                    manager: {label: 'Approbation du responsable', description: 'Les employé·e·s soumettent leurs rapports à leur responsable direct configuré dans Gusto.'},
+                    custom: {label: 'Approbation personnalisée', description: 'Je configurerai manuellement les circuits de validation dans Expensify.'},
                 },
                 connect: 'Connect',
                 connectionDescription: 'Connectez Gusto pour synchroniser les validations des employé·e·s avec votre espace de travail.',
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 7857c2a3..bebaf863 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -7016,24 +7016,15 @@ Aggiungi altre regole di spesa per proteggere il flusso di cassa aziendale.`,
                 approvalMode: 'Modalità approvazione',
                 finalApprover: 'Approvazione finale',
                 notSet: 'Non impostato',
-                approvalModeDescription: 'Membri e responsabili sono configurati per sincronizzarsi con Gusto.',
+                approvalModeDescription: 'I membri e i responsabili sono configurati per la sincronizzazione con Gusto.',
                 approvalModeWarningTitle: 'Cambiare modalità di approvazione?',
                 approvalModeWarningPrompt: (helpSiteURL: string) =>
-                    `Vuoi davvero cambiare la modalità di approvazione per questo spazio di lavoro? Scopri di più sulle diverse modalità di flusso di lavoro abilitate da Gusto nel nostro <a href="${helpSiteURL}">sito di assistenza</a>.`,
+                    `Sei sicuro di voler cambiare la modalità di approvazione per questo spazio di lavoro? Scopri di più sulle diverse modalità di flusso di lavoro abilitate per Gusto nel nostro <a href="${helpSiteURL}">sito di assistenza</a>.`,
                 approvalModeWarningConfirm: 'Cambia modalità di approvazione',
                 approvalModes: {
-                    basic: {
-                        label: 'Approvazione di base',
-                        description: 'Tutti gli utenti inviano a una sola persona per l’elaborazione e l’approvazione.',
-                    },
-                    manager: {
-                        label: 'Approvazione del manager',
-                        description: 'I dipendenti inviano i report al proprio manager diretto configurato in Gusto.',
-                    },
-                    custom: {
-                        label: 'Approvazione personalizzata',
-                        description: 'Configurerò manualmente i flussi di lavoro di approvazione in Expensify.',
-                    },
+                    basic: {label: 'Approvazione di base', description: 'Tutti gli utenti inviano a una singola persona per l’elaborazione e l’approvazione.'},
+                    manager: {label: 'Approvazione del responsabile', description: 'I dipendenti inviano i report al proprio responsabile diretto configurato in Gusto.'},
+                    custom: {label: 'Approvazione personalizzata', description: 'Imposterò manualmente i flussi di approvazione in Expensify.'},
                 },
                 connect: 'Collega',
                 connectionDescription: 'Collega Gusto per sincronizzare le approvazioni dei dipendenti con il tuo spazio di lavoro.',
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index 7afbf7d7..ceafe94e 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -6942,21 +6942,12 @@ ${reportName}
                 approvalModeDescription: 'メンバーとマネージャーは Gusto と同期するように設定されています。',
                 approvalModeWarningTitle: '承認モードを変更しますか?',
                 approvalModeWarningPrompt: (helpSiteURL: string) =>
-                    `このワークスペースの承認モードを変更してもよろしいですか? Gusto 対応の各ワークフローモードについて詳しくは、<a href="${helpSiteURL}">ヘルプサイト</a>をご覧ください。`,
+                    `このワークスペースの承認モードを変更してもよろしいですか?Gusto 対応の各ワークフローモードについては、<a href="${helpSiteURL}">ヘルプサイト</a>で詳しくご覧いただけます。`,
                 approvalModeWarningConfirm: '承認モードを変更',
                 approvalModes: {
-                    basic: {
-                        label: '基本承認',
-                        description: 'すべてのユーザーは、処理と承認のために1人の担当者に提出します。',
-                    },
-                    manager: {
-                        label: 'マネージャー承認',
-                        description: '従業員は、Gusto で設定された直属のマネージャーにレポートを提出します。',
-                    },
-                    custom: {
-                        label: 'カスタム承認',
-                        description: 'Expensify で承認ワークフローを手動で設定します。',
-                    },
+                    basic: {label: '基本承認', description: 'すべてのユーザーは、処理と承認のために 1 人の担当者に提出します。'},
+                    manager: {label: 'マネージャー承認', description: '従業員は、Gusto で設定された直属のマネージャーにレポートを提出します。'},
+                    custom: {label: 'カスタム承認', description: 'Expensify で承認ワークフローを手動で設定します。'},
                 },
                 connect: '接続',
                 connectionDescription: 'Gusto を接続して、従業員の承認をワークスペースと同期させましょう。',
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index d3655cb1..b7301b1b 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -6995,24 +6995,15 @@ er bestedingsregels toe om de kasstroom van het bedrijf te beschermen.`,
                 approvalMode: 'Goedkeuringsmodus',
                 finalApprover: 'Laatste fiatteur',
                 notSet: 'Niet ingesteld',
-                approvalModeDescription: 'Leden en managers zijn ingesteld om met Gusto te synchroniseren.',
+                approvalModeDescription: 'Leden en managers zijn ingesteld om te synchroniseren met Gusto.',
                 approvalModeWarningTitle: 'Goedkeuringsmodus wijzigen?',
                 approvalModeWarningPrompt: (helpSiteURL: string) =>
-                    `Weet je zeker dat je de goedkeuringsmodus voor deze werkruimte wilt wijzigen? Lees meer over de verschillende Gusto-werkstroommodi op onze <a href="${helpSiteURL}">helpsite</a>.`,
+                    `Weet je zeker dat je de goedkeuringsmodus voor deze werkruimte wilt wijzigen? Lees meer over de verschillende Gusto-ondersteunde workflowmodi op onze <a href="${helpSiteURL}">help-site</a>.`,
                 approvalModeWarningConfirm: 'Goedkeuringsmodus wijzigen',
                 approvalModes: {
-                    basic: {
-                        label: 'Basisgoedkeuring',
-                        description: 'Alle gebruikers dienen in bij één persoon voor verwerking en goedkeuring.',
-                    },
-                    manager: {
-                        label: 'Goedkeuring door manager',
-                        description: 'Medewerkers dienen rapporten in bij hun directe manager die in Gusto is geconfigureerd.',
-                    },
-                    custom: {
-                        label: 'Aangepaste goedkeuring',
-                        description: 'Ik stel goedkeuringswerkstromen handmatig in Expensify in.',
-                    },
+                    basic: {label: 'Basisgoedkeuring', description: 'Alle gebruikers dienen bij één persoon in voor verwerking en goedkeuring.'},
+                    manager: {label: 'Goedkeuring manager', description: 'Werknemers dienen rapporten in bij hun direct leidinggevende die is ingesteld in Gusto.'},
+                    custom: {label: 'Aangepaste goedkeuring', description: 'Ik stel goedkeuringsworkflows handmatig in in Expensify.'},
                 },
                 connect: 'Verbinden',
                 connectionDescription: 'Verbind Gusto om goedkeuringen van werknemers gesynchroniseerd te houden met je workspace.',
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 87b45349..9359cab9 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -6991,21 +6991,12 @@ Dodaj więcej zasad wydatków, żeby chronić płynność finansową firmy.`,
                 approvalModeDescription: 'Członkowie i menedżerowie są skonfigurowani do synchronizacji z Gusto.',
                 approvalModeWarningTitle: 'Zmienić tryb zatwierdzania?',
                 approvalModeWarningPrompt: (helpSiteURL: string) =>
-                    `Czy na pewno chcesz zmienić tryb zatwierdzania dla tej przestrzeni roboczej? Dowiedz się więcej o różnych trybach przepływu pracy obsługiwanych przez Gusto w naszej <a href="${helpSiteURL}">witrynie pomocy</a>.`,
+                    `Czy na pewno chcesz zmienić tryb zatwierdzania dla tego obszaru roboczego? Dowiedz się więcej o różnych trybach przepływu pracy obsługiwanych przez Gusto w naszej <a href="${helpSiteURL}">witrynie pomocy</a>.`,
                 approvalModeWarningConfirm: 'Zmień tryb zatwierdzania',
                 approvalModes: {
-                    basic: {
-                        label: 'Podstawowe zatwierdzanie',
-                        description: 'Wszyscy użytkownicy przesyłają do jednej osoby do przetworzenia i zatwierdzenia.',
-                    },
-                    manager: {
-                        label: 'Zatwierdzanie przez menedżera',
-                        description: 'Pracownicy przesyłają raporty do swojego bezpośredniego menedżera skonfigurowanego w Gusto.',
-                    },
-                    custom: {
-                        label: 'Niestandardowe zatwierdzanie',
-                        description: 'Ręcznie skonfiguruję procesy zatwierdzania w Expensify.',
-                    },
+                    basic: {label: 'Podstawowa akceptacja', description: 'Wszyscy użytkownicy przesyłają wydatki do jednej osoby w celu ich przetworzenia i zatwierdzenia.'},
+                    manager: {label: 'Zatwierdzenie przez menedżera', description: 'Pracownicy przesyłają raporty do swojego bezpośredniego menedżera skonfigurowanego w Gusto.'},
+                    custom: {label: 'Niestandardowa akceptacja', description: 'Ręcznie skonfiguruję procesy zatwierdzania w Expensify.'},
                 },
                 connect: 'Połącz',
                 connectionDescription: 'Połącz Gusto, aby synchronizować akceptacje pracowników z Twoim miejscem pracy.',
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 29d884ae..5da3a7a1 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -6997,21 +6997,12 @@ Adicione mais regras de gasto para proteger o fluxo de caixa da empresa.`,
                 approvalModeDescription: 'Membros e gerentes estão configurados para sincronizar com o Gusto.',
                 approvalModeWarningTitle: 'Alterar modo de aprovação?',
                 approvalModeWarningPrompt: (helpSiteURL: string) =>
-                    `Tem certeza de que deseja alterar o modo de aprovação deste espaço de trabalho? Saiba mais sobre os diferentes modos de fluxo de trabalho habilitados pelo Gusto em nosso <a href="${helpSiteURL}">site de ajuda</a>.`,
+                    `Tem certeza de que deseja alterar o modo de aprovação deste workspace? Saiba mais sobre os diferentes modos de fluxo de trabalho com Gusto em nosso <a href="${helpSiteURL}">site de ajuda</a>.`,
                 approvalModeWarningConfirm: 'Alterar modo de aprovação',
                 approvalModes: {
-                    basic: {
-                        label: 'Aprovação básica',
-                        description: 'Todos os usuários enviam para uma única pessoa para processamento e aprovação.',
-                    },
-                    manager: {
-                        label: 'Aprovação do gerente',
-                        description: 'Os funcionários enviam relatórios para o gerente direto configurado no Gusto.',
-                    },
-                    custom: {
-                        label: 'Aprovação personalizada',
-                        description: 'Vou configurar manualmente os fluxos de trabalho de aprovação no Expensify.',
-                    },
+                    basic: {label: 'Aprovação básica', description: 'Todos os usuários enviam para uma única pessoa para processamento e aprovação.'},
+                    manager: {label: 'Aprovação do gerente', description: 'Os funcionários enviam relatórios ao gestor direto configurado no Gusto.'},
+                    custom: {label: 'Aprovação personalizada', description: 'Vou configurar manualmente os fluxos de aprovação no Expensify.'},
                 },
                 connect: 'Conectar',
                 connectionDescription: 'Conecte o Gusto para manter as aprovações de funcionários sincronizadas com seu workspace.',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 2b64aa7e..c267cc73 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -6821,24 +6821,15 @@ ${reportName}
                 approvalMode: '审批模式',
                 finalApprover: '最终审批人',
                 notSet: '未设置',
-                approvalModeDescription: '成员和经理已设置为与 Gusto 同步。',
+                approvalModeDescription: '成员和管理员已设置为与 Gusto 同步。',
                 approvalModeWarningTitle: '更改审批模式?',
                 approvalModeWarningPrompt: (helpSiteURL: string) =>
-                    `你确定要更改此工作区的审批模式吗?请在我们的<a href="${helpSiteURL}">帮助网站</a>中了解更多关于不同 Gusto 启用工作流模式的信息。`,
+                    `您确定要更改此工作区的审批模式吗?在我们的<a href="${helpSiteURL}">帮助网站</a>中了解更多关于不同 Gusto 启用的工作流模式的信息。`,
                 approvalModeWarningConfirm: '更改审批模式',
                 approvalModes: {
-                    basic: {
-                        label: '基本审批',
-                        description: '所有用户都提交给同一个人进行处理和审批。',
-                    },
-                    manager: {
-                        label: '经理审批',
-                        description: '员工将报告提交给 Gusto 中配置的直属经理。',
-                    },
-                    custom: {
-                        label: '自定义审批',
-                        description: '我将在 Expensify 中手动设置审批工作流。',
-                    },
+                    basic: {label: '基础审批', description: '所有用户都提交给同一个人进行处理和审批。'},
+                    manager: {label: '经理审批', description: '员工会将报销单提交给在 Gusto 中配置的直属经理。'},
+                    custom: {label: '自定义审批', description: '我将在 Expensify 中手动设置审批工作流程。'},
                 },
                 connect: '连接',
                 connectionDescription: '连接 Gusto,以在您的工作区中同步员工审批。',

Note

You can apply these changes to your branch by copying the patch to your clipboard, then running pbpaste | git apply 😉

View workflow run

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.

3 participants