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.
Add Expiration Date for User Accounts in User Management
In the current user management system, there is no way to define a specific expiration date for a user’s access. I would like to propose adding an “Access Expiration Date” field to each user profile. 🔧 What the feature should do: Allow administrators to set a specific date on which a user’s access will automatically expire. After reaching that date, the user should be automatically deactivated or lose access without requiring any manual action. Ideally, the system should also: Display the expiration date in the user overview. Send optional notifications shortly before expiration (to admins and/or the user). Allow editing or extending the expiration date at any time. 🎯 Why this is useful: Makes it easier to manage temporary users (consultants, interns, project-based accounts, external partners). Prevents forgotten accounts from staying active longer than intended. Ensures better security and compliance. This feature would greatly simplify user lifecycle management and reduce manual administrative work.
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.
Do you get booted out of Support case drafts?
I would like to see the Support Portal not auto-refresh auto-log-me-out while I'm working in there. I too often get booted out of drafts of support tickets by being auto-ejected and logged out of the support portal and community site. I'm just actively typing along in the Case Comments box, and the page refreshes and I'm logged out, losing all my work in the process. Of course, this is my reminder to stop using the Support Portal UI for drafting my comments, but it's so tempting to just work the way I expect to be able to work, and then I forget and get burned.Additional Sisense CloudMS Upgrade Reminder
With most Dev/Prod Cloud Upgrade reminders often being sent 1-3 weeks ahead of time, a customer is respectfully requesting to add a second reminder preferably the day before the scheduled upgrade in order to make sure they are prepared and can make any changes to their resources or timelines.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.
