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

The Data Security tab's group/user assignment window currently has a max search limit of 20 results.   The "results" search limit should be configurable because we have approx. 50 groups that need to be assigned, & it is very difficult to find/assign/manage all of the groups when the search window does not return all of the appropriate results. ... View more

Idea: Allow developers to build/test add-ons in a local environment rather than requiring a live environment. Note that this would be for the purpose of creating custom add-ons for additional functionality that would require testing on the "out of the box" Sisense UI. Background/Context: In most development workflows it is common practice to work on your code locally on your machine and deploy to a local server aka "localhost" to test/view your work in the browser. An example of this is building and deploying a local React.js app to your browser. As you make changes to the code it will recompile locally and update what you see on your localhost. If you're using Sisense out of the box however, to test/view any changes to an add-on developers are forced to upload the files in some way to a live Sisense Environment. This not only limits the innovation of add-ons to developers with an active license and live environment, it makes it painfully inefficient to develop customizations on top of the Sisense application. I understand there are likely some business concerns with allowing the use of the product locally but I'd argue that there are ways to prevent that, such as enforcing some default sample data etc., but in such a way that would give developers a "local playground" to develop/innovate on. ... View more

When generating the WAT token, we need to pass the Sisense user ID in the 'sub' parameter. To obtain the user ID, we must repeatedly call the Sisense APIs, which can be inefficient. It would be beneficial if we could directly include the Sisense username or email in the 'sub' parameter, thereby avoiding unnecessary API calls to retrieve the Sisense user ID. Reference Document - https://docs.sisense.com/main/SisenseLinux/using-web-access-token.htm#StructuredTokensByValue ... View more

Some end-users have strict environmental and security constraints for their operations.  Please consider including M.I.T. Kerberos binaries and environment variable so that JDBC connectors could leverage Kerberos without having to access Kubernetes hosts machines. ... View more

I use Chrome browser. I keep multiple tabs of sisense opened. When the session expires, it expires on ALL the tabs (which makes total sense).  The problem is that all those tabs get redirected to the login page and I need to login on each and every one of them. It does not detect I've logged in in another tab, neither if I hit the browser Refresh button it will detect the login and redirect me to the page I was in before I got logged out.   This is annoying because I have to either login again, or open a new window and search for the dashboard I had open. Ideal expected behaviour (preferred, but probably harder): Once I'm logged out on several tabs, logging in one of them should make the others notice and log me in automatically. Good-enough behaviour ("easier"): Once I'm logged out on several tabs, logging in one of them should allow me to go to other opened tabs, which are showing the login windows, and refresh them (e.g using Ctrl+R) so that itwill automatically detect my session and redirect to the page I was before I was logged out.   This will save me a lot of time and make sisense less annoying. ... View more

It would be very helpful to be able to pass User or Group parameters as Claims in a Web Access Token. This will allow customers to leverage the dynamic features related to User/Group Parameters (e.g. dynamic live query) when using Web Access Tokens. ... View more