2026.1 Release Notes

For a list of release dates and Sisense's end of support schedule, see Sisense Version Release and Support Schedule.

For information about the Sisense gradual rollout process, as well as an explanation of how the versions and release notes relate to content added during the rollout, see Sisense Gradual Rollout Process.

2026.1.0 Release Overview

Pre-Release

These release notes are being provided in advance of the release, for your preparation and evaluation of the upcoming version. This version will be released for Cloud Availability shortly.

As the content is still in progress, it is recommended that you check back here occasionally for the latest updates.

Release 2026.1.0 provides a number of new features, improvements, and fixes to Sisense for Linux.

What's New

The following table lists the high-level impact (or potential impact, if any) of new features, and how to handle it if upgrading to version 2026.1.0 or newer. Continue reading the Release Notes below the table for a detailed explanation of these features, as well as improvements and fixes.

Feature	Issues and Actions to Consider
Two-Factor Authentication	Currently in Beta. See the complete documentation here.

Two-Factor Authentication

This release introduces email-based Two-Factor Authentication (2FA) for Sisense native users as a Beta feature.

When 2FA is enabled, before they can access Sisense, native users must provide:

1. Their Sisense username and password, and

2. A one-time password (OTP) sent to their registered email address

This significantly reduces the risk of unauthorized access due to leaked or reused credentials.

2FA is controlled at two levels:

• Deployment-wide (system) feature toggle - Enables or disables 2FA on the entire deployment.

• Per-user configuration – Controls whether a specific native user is required to complete 2FA at login.

The default values are false/off for both of the controls during this Beta stage.

The following is the login flow for a native user with Require Two-Factor Authentication: true when the global feature toggle is ON:

1. Enter your username and password on the standard Sisense login page.

   • After successful credential validation, Sisense displays a 2FA code screen.

   • Sisense generates a time-limited OTP and sends it to your registered email.

2. Enter the OTP on the 2FA screen.

   • If the OTP is valid and not expired, you are logged in.

For more information, see Email-Based Two-Factor Authentication (2FA) for Sisense Native Users (Beta).

What's Improved

Build To Destination (B2D)

• Build to Destination connections are now fully isolated from the regular data source connections managed via Connection Management. From now on, B2D connections can only be created or managed using B2D API endpoints.

Compose SDK Mode

• Calendar heatmap and Tabber widgets are now compatible with and supported in Compose SDK mode.

• The Compose SDK Mode feature is now enabled by default.

Connectors

• Previously, the Snowflake default authentication method was based on a PEM key which was stored unencrypted in the server filesystem. To enhance security Sisense now allows and defaults to authentication based on “private key content” which is encrypted and inaccessible to internal users once its saved.

• A new option was added for the Snowflake connector to paste the content of the private key instead of uploading the file into the server.

• The Databricks driver has been updated to version 3.0.1.

• The Singlestore-jdbc (MemSQL) driver has been upgraded to version 1.2.8.

Filters

• Custom filters now appear in a dedicated tab. Viewers and users with Can View permissions do not have access to the Custom tab unless advanced is set to true in permissions.

• 2 popular rank filters: “Top” and “Bottom” have been moved to the dedicated Rank tab. Viewers and users with Can View permissions do not have access to the Rank tab unless the user is editing a rank filter or modify_type is set to true in permissions.

Infra

• Sisense now supports Red Hat Enterprise Linux (RHEL) 10.

  Note: If you are running Red Hat 10 and are offline, you must install kernel-modules-extra before running the Sisense installation:

  sudo dnf install kernel-modules-extra-$(uname -r) -y

Sisense Version Naming and Schedule

Sisense version names and the release frequency is now as follows:

1. Major releases > released quarterly

2. Service packs > released monthly

3. Patches > released as needed on a case by case basis - e.g., fix to the released version, adjustment required by external changes, etc.

The letter “L” will no longer precede the version number.

The format is now: YEAR.QUARTER.SERVICE_PACK-PATCH

Examples:

• 2026.1.0 > first major release of 2026

• 2026.2.1 > first service pack for the second major release of 2026

• 2026.1.0-a > first patch to the first major release of 2026

What's Fixed

Add-ons

• Previously, when using Jump to Destination (JTD) in Shared Mode, the target dashboard filters did not refresh based on the selected widget. This has now been fixed and JTD works as expected in Shared Mode.

• Previously, filter relationships were not fully supported by Jump to Dashboard - some filters were not passed as expected. This has now been fixed and the filter relationships are transferred to the target dashboard, with all filters aligned. Note that if mergeTargetDashboardFilters is true and filterRelations exists, all filters passed to the target dashboard will be converted to single-level (non-cascading) filters.

Analytical Engine

• Previously, in some cases, filtering a dashboard or widget (for example orders totaling over 500) did not display filtered or sorted data correctly in the Analytical Engine. As a result, the dashboard and widgets did not display the correct data. This has now been fixed and filters in the AE operate as expected.

Assistant

• Previously, when clicking Add to Dashboard from the assistant, the widget was not always added to the dashboard. This has now been fixed and works as expected.

Compose SDK Mode

• An issue was fixed with Sisense Intelligence Forecast that rendered the forecast incorrectly in CSDK and CSDK mode.

Connectors

• Previously, under certain conditions, a race condition occurred in Snowflake during schema SWAP and DROP operations. This has been fixed and these commands are strictly serialized, ensuring data integrity and preventing accidental schema deletion during high-velocity deployments.

Git

• Committing large data models to Git now works as expected, as the limit was increased. Previously, attempts to commit very large assets (such as data models with hundreds of tables) would fail and return “PayloadTooLargeError,” blocking Git integration for big projects.

Narrative

• Previously, self-hosted users could change the narrative provider via API to a provider that is not available for them. This has now been fixed and unavailable providers cannot be designated.

Outer Joins

• Previously, outer joins in legacy models were being sent as-is in compatibility mode, causing inconsistencies. This has been fixed and when using compatibility mode all joins are automatically converted to inner joins, while preserving the original join types which are restored when switching back to the Analytical Engine (AE).

Reports

• Previously, when using the “Send me a report now“ option in Report Manager, the system did not add the date and time to the email header. This has been fixed and the email’s header now includes the date and time when the report was generated.

Reporting in WAT Flow

• Changed filters are now reflected in the exported PDF report of the dashboard accessed in the Web Access Token flow. Previously, filters were not applied, creating a discrepancy between the data in the dashboard and the exported PDF file.

Tenants

• Forgot password emails for tenants now work properly, even if SSO was enabled and later disabled. Previously, if SSO had been enabled for a tenant, users did not receive forgotten password emails, and attempts to reset passwords resulted in errors and no email was sent.

User Parameters

• Validation for null values has been added when creating user parameters via API - the request is not executed and an error is returned. Previously, the parameters were created and caused issues with editing such parameters in the UI.

User Roles

• It is now possible to change the role of admin created in the tenant. Previously, this option was blocked with the only remaining option being to delete and re-create the user with the correct role.

• Previously, in rare circumstances (such as cache expiration during API authentication), the SysAdmin’s role could be reset to a Viewer role, disrupting automation and scheduled tasks. This has now been fixed such that SysAdmin user roles now remain stable and are no longer unexpectedly downgraded to Viewer.

Web Access Token

• Accessing dashboards via Web Access Token (WAT) in the environment with the New Navigation Bar enabled now works as expected. Previously, the page failed to load with the error TypeError: Cannot read properties of null (reading 'getLogo') causing issues in corresponding WAT-based solutions.

Widgets

• After upgrading from 2025.3 to L2025.4.0.109, when a column's data type was configured as Text, empty cells within the table widget would occasionally display as "(blank)". This has been fixed, and the cells now appear empty.