ContributionsMost RecentNewest TopicsMost LikesSolutionsRe: 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! Deprecation Notice: Direct Access to Sisense Internal MongoDB Sisense is deprecating direct connections to its internal MongoDB and related data models to enhance stability, security, and scalability. This does not impact external or customer-managed MongoDB sources, which remain fully supported. Re: Build monitor Scheduled builds observability and orchestration is part of the backlog, but it has not been prioritised to share estimated release date. Can you share the most important metrics for you, so that we could extend existing usage analytics build dashboard meanwhile? Important update: connections management GA release & API behavior changes If you are using data model APIs, please read this post to ensure your solutions don't experience any disruptions 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. Re: Refresh schema for all tables Hi, I would like to inform that since L2024.3 there is ability to refresh scheme for all tables of data model in 1 action. Feel free to try it out through 3 dots context menu in the top right corner of the data model. Re: Sisense-Git Integration Issues Hi harni_sri, Thanks for reaching out and for sharing the feedback. Let me address your questions one by one "We have 2 environments dev & prod. When we develop a dashboard/model in dev using sisense GUI & push it to git-hub & merge it into the git hub master branch, we expected the master to reflect the changes in prod. Is there a sisense documentation that tells us how to integrate sisense via git hub across different environments i.e on how to connect the prod environment to git and do a git pull." Considering that the Sisense instance (dev, stage, prod, etc) is treated as a local repository - there is no difference in working with Git, as with any other software project. Meaning, that in order for the changes committed in Master on Dev env and pushed to the remote (GitHub) to be reflected in Prod env - you need to make pull. Check https://docs.sisense.com/main/SisenseLinux/introduction-to-sisense-git-integration.htm?tocpath=Git%20Integration%7C_____1#UsingacrossMultipleEnvironments and https://git-scm.com/docs/git-pull/en for reference "The performance of the GUI is very slow." Please, submit a ticket with clear steps to reproduce, details about assets used in the project and what exact action is performing slow to you. "When merged with master in git hub, it creates 2 new folders dashboards & data models & saves the assets along with their unique oid. Is there a way to store only the name of the dashboards /data models?" No, this is not possible, as both oid and name of the assets create the unique name of the file in the Git file system. This is a basement for Git to understand to which assets new commits should be applied. See https://docs.sisense.com/main/SisenseLinux/asset-translation-and-management.htm?tocpath=Git%20Integration%7C_____3#NamingConvention for more information. "When we manually import/export a dashboard or data model, we use only one file either a .dash /.smodel. But when done via GUI 14/15 files get selected for pushing a small change. Is there a way to select only changed files?" To improve performance and enhance the visibility of changes being made, Sisense assets (such as Data Models and Dashboards) are converted, or translated, into decomposed sets of child files in the JSON format. For more info check https://docs.sisense.com/main/SisenseLinux/asset-translation-and-management.htm?tocpath=Git%20Integration%7C_____3#ConversionStrategy You may create smaller commits and push/pull them if you want smaller increments of changes to be delivered between the environments. Let me know if that answers your question. Re: Global ElastiCube Builds Schedule Report Hi goillocorcent, Thanks for sharing your feedback with us. It is vital for us! We already have Scheduled Builds Orchestration as part of the H2 2024 roadmap and will make sure to consider your feedback. Please, stay updated with the release notes. Re: Data Source Dependency Report dougnewton, thank you for sharing the feedback and submitting this request. This is vital for us! We will make sure to investigate it and add a straightforward ability to get this information in the UI for the users. Will keep you updated!