Alternate authentication method for different tenants

m3ac-johnsonb · ‎10-31-2024

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.

filski · ‎10-17-2024

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.

fschleich · ‎08-31-2023

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

joeshepper · ‎01-23-2024

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.

joeshepper · ‎01-23-2024

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.

markd · ‎07-28-2023

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.

pbrooksSDL · ‎10-20-2023

Currently a user can only have access to one tenant at a time. In my organisation we are only able to log into Sisense with an AD account, so users can only have one login each. All of our reporting and elasticubes are currently on the one original System tenant. I need to set up a second tenant to hold some highly confidential elasticubes and then be able to grant access to this tenant to a select few users, but with them still retaining access to the original system tenant. The current setup means these users would lose access to all of their other dashboards on the original tenant.

sumana · ‎10-12-2023

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.

Sisense Community

Alternate authentication method for different tenants

Allow for Usage Analytics within self-contained multitenancy

Multitenant : Define a different sender for email notifications

Change Email Text for Tenant

Change Website URL Whitelabelling For Tenants

Add a specific CSV row limit for Report Manager

User able to log into more than one tenant

Feature to export all datamodels from UI