Oleksandr_K
Sisense Employee
Joined 4 years ago
User Profile
User Widgets
Contributions
Re: Two-factor authentication - Status changed to: Planned
Hi, I’m happy to share that Two-Factor Authentication (2FA) is currently in active development and is planned for release in early 2026. (We will, of course, do our best to deliver it sooner if possible!) I would like to share the major implementation concepts: Who is this for? 2FA will apply to native Sisense users only - those created in Sisense Admin and who log in with a Sisense username and password. Active Directory (AD) or Single Sign-On (SSO) users will be excluded. This is intentional, as their authentication (including any MFA) is configured and managed by their external identity provider. Where will it be available? 2FA will be available for both cloud and on-prem deployments, as long as an email server is configured for your instance. What is the second factor? The second factor will be a secure, one-time code sent to the user’s email. Support for other methods (such as authenticator apps or SMS) is not planned at the moment. How will I control the rollout? This was a key part of your feedback. To ensure a smooth rollout and flexible control, we are implementing two levels of management: System-Level Toggle: The master switch that enables or disables 2FA across your entire deployment. User-Level Configuration: Determines whether 2FA is required for an individual user. Admins will be able to manage individual user configurations through a “Require Two-Factor Authentication” control in the Users list (GUI) or via the API. The default value will be ON, allowing easy and secure enablement for the majority of users while still providing flexibility for exceptions (e.g., system, integration, or QA accounts).Re: Dashboards as Code With Sisense Git Integration
Hi chaobibtc, thanks so much for sharing your experience! 🙌 It’s great to see how Sisense Git Integration is helping streamline your version control and asset promotion workflows. 🔥 I’d like to briefly comment on the following point you raised: "If Elasticubes are used, ensure data connection names are consistent across environments. Mismatches can cause sync or deployment failures." Since Git integration is based on the file system, we rely on the OID (object ID) as the unique identifier for assets, not the asset names, which can be duplicated. This means that dashboard, data model, and connection OIDs remain consistent when promoting assets across environments. You can check out the recommended and supported approach for working with connections in our documentation here- https://docs.sisense.com/main/SisenseLinux/data-source-connection-management.htm#GitIntegrationPromotion Please feel free to share any additional feedback or submit feature requests directly in the community — we’re always listening!Re: Sisense Fusion git limits
Thank you for reaching out! In Sisense Fusion, there is no explicit 500MB size limit on Git repositories at the file system level. However, extremely large repositories can introduce performance challenges in terms of how the application interacts and synchronizes with Git. Additionally, Fusion’s Git integration currently supports only dashboards and data model metadata—other asset types aren’t tracked or processed, even if they’re manually added to the repository. I’d be happy to learn more about your specific use case to understand why your repository needs to be this large and discuss any potential workarounds or best practices to optimize performance.
