diff --git a/blog/260217-multi-entity-portal-update.md b/blog/260217-multi-entity-portal-update.md index b1d85ba21..ee139fcd8 100644 --- a/blog/260217-multi-entity-portal-update.md +++ b/blog/260217-multi-entity-portal-update.md @@ -17,19 +17,18 @@ On **February 25, 2026**, we are changing how multi-entity companies are display We are introducing the following improvements: -- Parent–child hierarchy view enables users to quickly identify the parent company and expand the view to see its subsidiaries. -- Enhanced search functionality allows users to search by the parent or child company name. +- Parent–child hierarchy view enables users to quickly identify the parent company and expand the view to see its subsidiaries. +- Enhanced search functionality allows users to search by the parent or child company name. - New triple-dot menu contains company management options, such as editing and deletion. - Connected software list is displayed when hovering over a company's connection status. - Parent deletion confirmation ensures it's no longer possible to accidentally delete a parent company. - New set of connection statuses helps determine a company's state at a glance: - - - **No connections:** The company hasn't yet attempted to connect their financial software. - - **Linked:** The company has successfully connected their financial software. - - **Pending:** The company has started, but not completed connecting their financial software. - - **Deauthorized:** The company has revoked your access, or the access expired. The company needs to be reconnected. - - **Unlinked:** You have unlinked this company's connection, and data sharing stopped as a result. - - **Partial:** The parent company has subsidiaries that are disconnected. + - **No connections:** The company hasn't yet attempted to connect their financial software. + - **Linked:** The company has successfully connected their financial software. + - **Pending:** The company has started, but not completed connecting their financial software. + - **Deauthorized:** The company has revoked your access, or the access expired. The company needs to be reconnected. + - **Unlinked:** You have unlinked this company's connection, and data sharing stopped as a result. + - **Partial:** The parent company has subsidiaries that are disconnected. These improvements apply to all Portal views that use the company structure, such as **Companies** and **Spend Insights**. diff --git a/blog/260217-spend-insights-portal-update.md b/blog/260217-spend-insights-portal-update.md index 2f8f07512..4b2327a2d 100644 --- a/blog/260217-spend-insights-portal-update.md +++ b/blog/260217-spend-insights-portal-update.md @@ -11,7 +11,7 @@ From **February 25, 2026**, you will be able to generate updated reports directl ## What's new? -We are enhancing the Spend Insights tab of the [Codat Portal](https://app.codat.io) so that you can manage, refresh, and export reports faster and at scale. +We are enhancing the Spend Insights tab of the [Codat Portal](https://app.codat.io) so that you can manage, refresh, and export reports faster and at scale. From **February 25, 2026**, you will be able to generate updated reports directly from the [Spend Insights](https://app.codat.io/spend-insights) tab by following these steps: @@ -23,13 +23,13 @@ From **February 25, 2026**, you will be able to generate updated reports directl 4. Click **Update reports** in the dropdown menu. -5. Track the progress by checking the *Report Status* column. Once updated, the status will change from *Generating* to *Available*. +5. Track the progress by checking the _Report Status_ column. Once updated, the status will change from _Generating_ to _Available_. 6. Click the **Download** icon again, then click on the report line item to save it. ![Improved Spend Insights report generation interface](/img/updates/260217-spend-insights-reports.gif) -We are also centralizing the company creation functionality. To create a new company, navigate to **Companies** in the navigation bar and click **Create company**. +We are also centralizing the company creation functionality. To create a new company, navigate to **Companies** in the navigation bar and click **Create company**. ## Who is this relevant for? @@ -37,6 +37,6 @@ This update is relevant for all [Spend Insights](/spend-insights/overview) clien ## How to get started? -If you are already using our [Spend Insights](/spend-insights/overview) solution, no further action is required. This update will automatically be available to you from **February 25, 2026**. +If you are already using our [Spend Insights](/spend-insights/overview) solution, no further action is required. This update will automatically be available to you from **February 25, 2026**. -If you want to start using our [Spend Insights](/spend-insights/overview) solution, reach out to your account manager. \ No newline at end of file +If you want to start using our [Spend Insights](/spend-insights/overview) solution, reach out to your account manager. diff --git a/blog/260218-link-branding-updates.md b/blog/260218-link-branding-updates.md new file mode 100644 index 000000000..7c77e3ce0 --- /dev/null +++ b/blog/260218-link-branding-updates.md @@ -0,0 +1,87 @@ +--- +title: "Enhanced company branding in Link" +date: "2026-02-18" +tags: ["Product", "Update", "Link"] +authors: pmckinney +--- + +We've expanded Link's branding options, making it easier than ever to deliver a fully branded authorization experience that feels like a native part of your product. + + + +## What's new? + +We've added new branding settings that give you greater control over how [Link](/auth-flow/overview) looks and feels to your customers. These updates are designed to help you create a seamless, trusted connection experience that reinforces your brand at every step. + +
+
+ Link without any branding applied +

+ Without branding +

+
+
+ Link branded using company logo, color scheme and hero image +

+ With branding +

+
+
+ +### Company logo on landing page + +You can now prominently display the logo from your existing [Branding](/auth-flow/customize/branding) settings on the first connection screen your customers see. + +Navigate to **Settings > Auth flow > Link > Onboarding** in the [Codat Portal](https://app.codat.io/settings/link-settings/onboarding) and enable the _Company logo_ setting. You must also have the _Landing page_ toggle enabled. + +### Navigation bar + +The new _Navigation bar_ setting adds a branded bar to the top of the Link flow using your secondary brand color, reinforcing your identity throughout the entire journey. + +Navigate to **Settings > Auth flow > Link > Onboarding** in the [Codat Portal](https://app.codat.io/settings/link-settings/onboarding) to enable this setting. + +### Secondary color + +You can now set a _Secondary color_, exercising finer control over the look and feel of the connection flow. This color is used by the new [Navigation bar](/updates/260218-link-branding-updates#navigation-bar) element of the Link flow. + +Navigate to **Settings > Auth flow > Branding** in the [Codat Portal](https://app.codat.io/settings/branding) to configure this setting. + +### Hero image + +Add a background to the main content area of Link using the _Hero image_ setting. This lets you set the visual tone of the authorization experience from the moment your customers land on the page. + +Navigate to **Settings > Auth flow > Branding** in the [Codat Portal](https://app.codat.io/settings/branding) to configure this setting. + +### Why does this matter? + +Customizing Link to further match your branding guidelines helps achieve the following outcomes: + +- **Increased trust:** Your customers are more likely to connect their financial data when they see familiar branding from the first screen. +- **Improved conversion:** A cohesive branded interface reduces friction and hesitation during the onboarding flow, helping you convert more customers. +- **Seamless experience:** These settings work together to create a connection experience that feels like a native part of your product, not a third party tool. + +## Who is this relevant for? + +This update is relevant for all clients using [Link](/auth-flow/overview) to connect their customers' financial data. It's especially valuable if you are looking to improve conversion rates and deliver a polished onboarding experience. + +## How to get started? + +The new branding settings are already available in the [Codat Portal](https://app.codat.io): + +1. Navigate to **[Settings > Auth flow > Link > Onboarding](https://app.codat.io/settings/link-settings/onboarding)** to enable the _Company logo_ and _Navigation bar_ toggles. +2. Set your _Company logo_, _Secondary color_, and _Hero image_ in **[Settings > Auth flow > Branding](https://app.codat.io/settings/branding)**. + +For more details, see our documentation on [Branding settings](/auth-flow/customize/branding) and [Link settings](/auth-flow/customize/customize-link). diff --git a/docs/auth-flow/customize/branding.md b/docs/auth-flow/customize/branding.md index e53efb88a..c61f15a7e 100644 --- a/docs/auth-flow/customize/branding.md +++ b/docs/auth-flow/customize/branding.md @@ -7,9 +7,35 @@ banner_image: "/img/banners/link.png" ## Overview -Link is a white-labelled solution that can be matched to your company's branding. Go to **[Settings > Auth flow > Branding](https://app.codat.io/settings/branding)** in the [Codat Portal](https://app.codat.io) to tailor Link for a fully custom-branded experience. - -The branding settings page autosaves when changes are made. You can adjust the following UI elements: +Link is a white-labelled solution that can be matched to your company's branding. Go to **[Settings > Auth flow > Branding](https://app.codat.io/settings/branding)** in the [Codat Portal](https://app.codat.io) to tailor Link for a fully custom-branded experience. The branding settings page autosaves when changes are made. + +
+
+ Link without any branding applied +

+ Without branding +

+
+
+ Link branded using company logo, color scheme and hero image +

+ With branding +

+
+
### Company name @@ -35,14 +61,33 @@ Icon requirements: - Files should not exceed 500KB. - Recommended dimensions: 32px x 32px. +### Hero image + +This image is displayed as a background in Link, appearing behind the main content area. + +Hero image requirements: + +- Use PNG, JPG, or JPEG file formats. +- Files should not exceed 10MB. +- Recommended dimensions: 1920px x 1080px. + ### Primary color You can set your brand's primary color to define the color of buttons and other elements within the Link Flow. We recommend using a dark primary color, because light colors may cause accessibility issues. -Branding settings screen with company name, logo, icon, and color picker displayed +### Secondary color + +You can set your brand's secondary color, which is used for the navigation bar in Link. The navigation bar can be enabled in [Link settings](/auth-flow/customize/customize-link#navigation-bar). + +
+ Branding settings screen with company name, logo, icon, hero image and color picker displayed +

+ Branding settings in the Codat Portal +

+
--- diff --git a/docs/auth-flow/customize/customize-link.md b/docs/auth-flow/customize/customize-link.md index 34dc829c7..fd27b1ea2 100644 --- a/docs/auth-flow/customize/customize-link.md +++ b/docs/auth-flow/customize/customize-link.md @@ -64,11 +64,9 @@ Let your users know that some integrations are not optimized or will not connect Toggle whether the _Secured by Codat_ logo is shown on your authorization flow. -#### Restart journey +#### Navigation bar -Allow your customers to restart the linking process for accounting software in case their first connection attempt fails. Enabling this setting will add a "Try again" button to the connection error page. - -It's possible to restart the linking process for commerce and banking platforms by default and no additional settings are required. +Toggle whether a navigation bar is displayed at the top of the Link flow. The bar color uses the secondary brand color you set in [Branding settings](/auth-flow/customize/branding#secondary-color). #### Landing page diff --git a/docs/commerce/error-documentation.md b/docs/commerce/error-documentation.md index 351ba45bd..8d064b79e 100644 --- a/docs/commerce/error-documentation.md +++ b/docs/commerce/error-documentation.md @@ -38,7 +38,7 @@ This section describes the errors that are related to Sync for Commerce configur | Error message | Error resolution | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Company needs to have two valid data connections. | This error surfaces if a company doesn't have 2 valid data connections **OR** both data connections do not have the `linked` status.
Ensure that the Codat company created for the merchant has 2 valid data connections. One commerce and one accounting connection are required.
Ensure that the Codat company has both data connection statuses set to `linked` by using the public API connection resource **OR** via the-no code merchant link journey using the link URL generated by the Codat app portal. | +| Company needs to have two valid data connections. | This error surfaces if a company doesn't have 2 valid data connections **OR** both data connections do not have the `linked` status.
Ensure that the Codat company created for the merchant has 2 valid data connections. One commerce and one accounting connection are required.
Ensure that the Codat company has both data connection statuses set to `linked` by using the public API connection resource **OR** via the-no code merchant link journey using the link URL generated by the Codat app portal. | | To sync fees:
- Payments section needs to exist
- Payments account id needs to be set | The **Fees** feature cannot be used until the **Payment** feature is configured.
The merchant should complete the configuration of Payments in order to sync Fees. | | Payments config invalid. `{prepaid account}` should not match `{prepaid payment account}`.
Accounts config invalid. Prepaid account in Sales should not match `{CommerceAccountType. PrepaidPayment}` in Payments." | The prepaid account and the payment account should not be the same.
Reconfigure the selected accounts for prepaid and prepaid payments. | | Payments config invalid. `{Card Acount}` should not match `{Payout Account}`. | This error surfaces if the account selected for Payments matches the payout account.
Reconfigure the selected accounts for payments and payouts. | diff --git a/docs/core-concepts/connections.md b/docs/core-concepts/connections.md index bd3f39c35..89abc36c4 100644 --- a/docs/core-concepts/connections.md +++ b/docs/core-concepts/connections.md @@ -24,13 +24,13 @@ Before you can use a data connection to read or write data, the company must gra Connections can have one of the statuses described in the following table. -| Status | Definition | -| :------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Linked` | The connection is linked to a data source; you can use it to read and write a company's consented data to and from the underlying provider's platform. | -| `PendingAuth` | The company hasn't authorized access to their financial platform (the data source). The SMB customer selected the platform in Link but did not complete the authorization flow. | -| `Deauthorized` | The connection was linked but is no longer able to access data from the underlying provider's platform.
You can access any data that was already read or written using this data connection. However, you can't perform any new read or write operations until the connection is re-linked.
A data connection usually becomes Deauthorized if the company revoked your access or an expiry time was reached. | +| Status | Definition | +| :------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `Linked` | The connection is linked to a data source; you can use it to read and write a company's consented data to and from the underlying provider's platform. | +| `PendingAuth` | The company hasn't authorized access to their financial platform (the data source). The SMB customer selected the platform in Link but did not complete the authorization flow. | +| `Deauthorized` | The connection was linked but is no longer able to access data from the underlying provider's platform.
You can access any data that was already read or written using this data connection. However, you can't perform any new read or write operations until the connection is re-linked.
A data connection usually becomes Deauthorized if the company revoked your access or an expiry time was reached. | | `Unlinked` | The data connection was previously linked, but you have severed the connection and gave up your access. (see [Disconnect a data connection to revoke your access to a data source](/core-concepts/connections#disconnect-a-data-connection-to-revoke-your-access-to-a-data-source)).
Similar to Deauthorized, you can still access any data that was already read or written using the data connection, but can't perform any new read or write operations unless the connection is re-linked. | -| No connections | The company has been created but does not have any connections to financial platforms established in any of the above statuses. | +| No connections | The company has been created but does not have any connections to financial platforms established in any of the above statuses. | ## Linked data connection example diff --git a/docs/integrations/accounting/quickbooksonline/accounting-quickbooksonline.md b/docs/integrations/accounting/quickbooksonline/accounting-quickbooksonline.md index e4817f437..e29221594 100644 --- a/docs/integrations/accounting/quickbooksonline/accounting-quickbooksonline.md +++ b/docs/integrations/accounting/quickbooksonline/accounting-quickbooksonline.md @@ -26,7 +26,7 @@ If you plan to publish an app in the QuickBooks ecosystem, you must register wit The Intuit App Partner Program operates a tiered usage model. Under this model, Intuit classifies API calls into two categories: - Core API calls - free and unlimited routine tasks, such as creating or updating invoices, bills, and customers -- CorePlus API calls - data-heavy tasks, such as running reports or retrieving deep historical data +- CorePlus API calls - data-heavy tasks, such as running reports or retrieving deep historical data The [API classification for the Intuit App Partner Program](https://help.developer.intuit.com/s/article/API-classification-for-the-Intuit-App-Partner-Program) article explains how API calls are classified into Core and CorePlus. @@ -41,7 +41,7 @@ Each tier is allocated a monthly limit of CorePlus API calls, and exceeding this To avoid unexpected costs, track your app's usage of API calls following these steps: 1. Log in to the [Intuit Developer Portal](https://developer.intuit.com/dashboard?tab=apps). -2. Navigate to the _App dashboard_ and select the app you want to review. +2. Navigate to the _App dashboard_ and select the app you want to review. 3. In the left-hand menu, click **Analytics**. 4. In _Analytics_, toggle the environment to **Production**. You will see a chart detailing your Core and CorePlus usage. diff --git a/docs/integrations/accounting/quickbooksonline/qbo-app-assessment-questionnaire.md b/docs/integrations/accounting/quickbooksonline/qbo-app-assessment-questionnaire.md index a5fd0a69d..f5b8faed1 100644 --- a/docs/integrations/accounting/quickbooksonline/qbo-app-assessment-questionnaire.md +++ b/docs/integrations/accounting/quickbooksonline/qbo-app-assessment-questionnaire.md @@ -32,7 +32,7 @@ This question should be answered by the app's developer. This question should be answered by the app's developer based on the guidelines provided below. - **Host domain**: the URL of the domain host of your website or app. - + - **Launch URL**: Initial URL for your app's authorization flow. If using [Hosted Link](/auth-flow/authorize-hosted-link), provide the generic Link URL from the [Codat Portal](https://app.codat.io). - **Disconnect URL**: Link to the process for deauthorizing the app's access to QBO. This can be the URL of the [Unlink connection](/platform-api#/operations/unlink-connection) endpoint or a link to your website or app instead. diff --git a/docs/knowledge-base/advanced-sync-settings.md b/docs/knowledge-base/advanced-sync-settings.md index 8aecba49a..c3e75b688 100644 --- a/docs/knowledge-base/advanced-sync-settings.md +++ b/docs/knowledge-base/advanced-sync-settings.md @@ -4,9 +4,9 @@ description: "Review additional settings available to configure the sync of vari displayed_sidebar: "docs" --- -For most of our data types, we retrieve all available history. For financial statement data types, (`balanceSheet`, `profitAndLoss`, `cashFlowStatement`), we retrieve 24 months of history. +For most of our data types, we retrieve all available history. For financial statement data types, (`balanceSheet`, `profitAndLoss`, `cashFlowStatement`), we retrieve 24 months of history. -You can apply additional sync settings to change these defaults. This helps you to limit the amount of data synchronized from the source platform. We recommend that you only pull data from a date range relevant to your use case to reduce the chance of encountering rate limit errors. +You can apply additional sync settings to change these defaults. This helps you to limit the amount of data synchronized from the source platform. We recommend that you only pull data from a date range relevant to your use case to reduce the chance of encountering rate limit errors. :::caution Limited coverage diff --git a/static/img/auth-flow/branded-link.png b/static/img/auth-flow/branded-link.png new file mode 100644 index 000000000..1ac94bd92 --- /dev/null +++ b/static/img/auth-flow/branded-link.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a7debba72c35d61ab81076aaebac92ae37d50be8a7ba579d84535da6d9aecc69 +size 1260661 diff --git a/static/img/auth-flow/branding.png b/static/img/auth-flow/branding.png new file mode 100644 index 000000000..547849c7d --- /dev/null +++ b/static/img/auth-flow/branding.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c8a39e3d1e843981310d672146d0a232022b04fae19108c8bf5cc5f102bb9120 +size 141290 diff --git a/static/img/auth-flow/unbranded-link.png b/static/img/auth-flow/unbranded-link.png new file mode 100644 index 000000000..8accf96f7 --- /dev/null +++ b/static/img/auth-flow/unbranded-link.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6afe837f4e9e318cd9fdc79d85004c49ba8ac0ed509024872b27e1a6b82c82e4 +size 49636 diff --git a/static/img/old/1cef143-branding.PNG b/static/img/old/1cef143-branding.PNG deleted file mode 100644 index 9f90e0252..000000000 --- a/static/img/old/1cef143-branding.PNG +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:08c5fd269658804188a28cad4aa29feea8f32d3bb41c1f284b2429d2f73a899a -size 38530