There needs to be a way to deactivate user accounts rather than completing removing. We have users that will no longer have access to the system, but could come back later (for example, trail users). The workarounds are currently: reassigning security groups (means those users are still taking up licenses) writing our own user admin functionality (only makes sense if we are integrating users to another platform) Adding a 'Status' or 'Disabled' flag to the user account would accomplish this. ... View more

Currently, ReportManager is only availbale on the system tenant, not on additionnal tenants. Could we have it for every tenants ?   Thank you, Franck ... View more

Custom Code is currently disabled in a multi-tenant environment, which is an odd thing to disable as it is among the many features that make Sisense so great because of the ability to manipulate the data within Sisense and part of the Tranform stage of ETL processes.  I am a Tenant Admin in my multi-tenant environment and I can click on Custom Code but I am not able to access the jupyter notebook environment. This creates a lot of confusion for clients who have multi-tenant environments and also takes a feature that the other clients have in single-tenant environments.  Sisense should seriously consider making this a permanent feature in all environments because it is so useful.  ... View more

Hello, In a multitenancy environment, it would be useful to be able to define different "look and feel" theme for each tenant. Currently, the one define on the system tenant is applied to every tenant. Thank you. ... View more

Looking for a way to change the logo based on their corresponding theme. We can create themes for the different companies but there is no option for logo in the Theme and would like to capability to extend the white labeling past just 1 logo ... View more

When creating a widget in SimplyAsk, We would like to see the download option extended to offer exporting to excel/CSV if the table viz is the best option. Some viewers might not be able to pin it to the dashboard but still want to extract the insights.  ... View more

It would be great if we were able to setup Active Directory for an individual tenant while having SSO enabled for another tenant. This would help us differentiate between our external customer facing and internal BI. ... View more

At the moment, the usage analytics functionality is only available for the system tenant. You can monitor activity across all tenants from there. However, this means that you cannot share usage analytics data with designers within the self-contained tenant. ... View more

Hello, In a multitenancy environment, it would be useful to be able to define an email notifications sender per tenant. ie : Tenant "Tenant A" : mail sender is "Sisense - A" Tenant "Tenant B" : mail sender is "Sisense - B" For now, email setup is only available from the default tenant, therefore unique accros all tenants. Thank you. Franck ... View more

We have tried increasing the row limit for CSV download of live models to 250K rows but Report Manager is still limiting output to 5,000 rows which is the query setting of live models. We would appreciate a specific setting for Report Manager that determines the number of rows or have RM use the row limit defined for the report type (in this case CSV and 250K rows). Changing the query limit for the model does impact the report manager, but this impacts all users and every UI interaction, so the data retrieval volume explodes. There should be an independent setting related to report generation. ... View more

Various features in Sisense can be whitelabelled. However, as well as the website, email notifications are another area of Sisense that customers will interact with. Email text configuration can be controlled via the 'email-templates.js' file, but there is not currently a way to whitelabel this text. I would like the option to change this text a deliver different messages for tenants. This would be useful for things like platform invitations in particular, to reassure users that an invitation from a 'Sisense' platform they may be unfamiliar with, is in fact associated with their company. ... View more

Sisense has some powerful whitelabelling features, but a key 'weak point' here is the URL itself. Currently, any Tenant has to be after the URL, e.g. for a company 'newcompany' at our company (Shepper), the URL would be shepper.sisense.com/newcompany. If we are delivering a whitelabelled solution for 'newcompany', where they want to whitelabel with newcompany assets only, there is no way to whitelabel the URL itself. I would like to keep the 'Shepper' text for most of our customers, but having an option to have an alternative URL for a tenant, such as newcompany.sisense.com (or even something that obscures our company's name a little, like shp.sisense.com/newcompany), would be the last piece of this whitelabelling puzzle. ... View more

We propose adding a valuable feature to our dashboard UI: the ability to export a comprehensive list of all data models, including both Elasticubes and live models. This enhancement is essential for efficiently monitoring model changes before and after Sisense upgrades. Presently, this process involves manual actions like taking screenshots or exporting a text file using 'si' commands, but it lacks the capability to export live models and essential metadata such as data model type, owner, last modification date, last publication date, activity, and size. By introducing export functionality in formats like CSV, users will be equipped to easily track and compare models, quickly identifying any discrepancies or replacements. This improvement will significantly streamline model management and ensure seamless transitions during upgrades. ... View more