/dashboards/admin not working on Linux 2025.3
Hello, We have been using Linux version 2025.2 and having no issues with the endpoint "/dashboards/admin". Now, we upgraded to 2025.3 and the "/dashboards/admin" endpoint is returning 500 error code 'Internal Server Error'. Other endpoints are working as expected. Wondering if there is a new endpoint to be using now, or some server setting we need to adjust. Appreciate the any assistance.
Add robust folder management
We have created many folders (and subfolders) to help us organize our dashboards. It is currently very cumbersome to share folder access and ownership, which must be done for every dashboard within the folders. It would be nice if there were an easy (and native) way to share access to a folder and every dashboard within it, or to change ownership of a folder.Update Connection Management API to allow the ability to automate updating Key's
Currently the connection management API allows a user to update connection information in an automated way. But when using KeyPair auth as Snowflake will be requiring very soon - we cannot use the same API to update the physical key. The current flow requires an admin to manually update a key by copy and pasting it into the file management. It is incredibly tedious and cumbersome for a user to have to update these one by one. I imagine more Sisense customers will realize this pain as the Snowflake timeline for KeyPair auth nears.
Add email operations to the Audit Logs
In an effort to simplify our troubleshooting of email issues, I would like to see email operations added into the Audit Logs. That enhancement, coupled with others like Make the time scope of Generate a Log File configurable | Sisense Community and Access various logs from Sisense UI under file management option | Sisense Community could greatly enhance our ability to support ourselves and reduce our support ticket submissions.Make the time scope of Generate a Log File configurable
We often need to troubleshoot an issue that wasn't reported to us within the 10-hour time frame covered by the Generating Support Log Files feature. We'd like to see the scope of time included in that file be configurable so that we can when need to, extend it to 48-hours or whatever we need to capture the events necessary for troubleshooting. Then set it back to whatever we wish as our default, which might be 2 hours. I want to acknowledge this idea [Access various logs from Sisense UI under file management option | Sisense Community] as I presume it would also cover the need if the full history of logs within Sisense's own retention policies are made available. But I do, sometimes, also like having a combined file to see events from different logs happing in concurrence without having to reference many different files.
Sisense Intelligence token estimation
Hi. We are considering activating Sisense intelligence to use a LLM for our data models and dashboards. We want to estimate how much this would our organization from the LLM provider side. It depends on the tokens that are input into the model. In the Sisense documentation it mentions that depends on the number of tables and column of the model, but I guess also on the pre-instructions text that is sent along the user's input. Is there a way of knowing how many tokens are added, or how much would cost to create a medium size dashboard given the OpenAI pricing? Thanks, Javi.
