dirons
Cloud Apps
Joined 3 years ago
User Profile
User Widgets
Contributions
Allow a user to remove themselves from a Shared dashboard (based on model) with email notification
We are a multi-tenant software provider and we embed and white label Sisense. In our setup, we have 2 models. Model 1 is used by Engineering to create our pre-built dashboards, where we share these with specific groups we've set up so that all of our customers see our pre-built "out of the box" dashboards The second model is what we expose to our Premium users so that they can create their own custom dashboards. There are times when our customers will create a new, custom dashboard with the second model. These users sometimes share their dashboard very broadly. When this happens, there are certain users that wish to remove themselves from the share. Perhaps they don't have row-level security to see anything. Perhaps they have changed roles or simply do not use that dashboard. Note that we do not want to allow customers to remove themselves from our pre-built shared dashboards, as this could cause support confusion as to why our analytics solution is enabled but a user doesn't see "all of the dashboards". With the above noted, we would like a configurable means to show/hide a "leave shared dashboard" dashboard option, based on the model with which a dashboard is associated. This will ensure that users cannot remove themselves from our pre-built dashboards (we would hide on our model) yet allow them to remove themselves from custom dashboards that were shared with them (we would show on model 2 for self-authoring) When a user leaves a shared dashboard, there should also be configuration options to alert the owner of the dashboard via email. This email should be capable of white labeling. It should include dashboard name, who left, and when. Should there be links to the dashboard in the email, there must be a way to disable hyperlinks in the email.770Views5likes1CommentFavorite dashboard
We produce pre-built dashboards for our customers. They can build their own as well. Often, they will start with one of our pre-built dashboards and modify to their needs. Users want a way to "filter out" our pre-built once they have created their own. One mechanism mentioned was the ability to "Favorite" a dashboard and have a new "Favorites" toggle on the Analytics tab.1.6KViews9likes7CommentsAbility for column level security to show/hide shared formulas as it can with attributes
We support multiple applications of data within a model, as there is crossover between the applications; however, our customers have granularity to choose which application data with which they are allowed to see when they create new dashboards. We use column level security for attributes today so that Application A author can only see table of data pertaining to application A while Application B author can only see tables of data pertaining to application B (note that a user can have both author rights and see all both application data). We found that this does not pertain to Shared Formulas. This now increases the "noise" that authors see, as they are seeing formulas for an application that isn't something they can readily use.1.8KViews6likes2CommentsAllow Designers to create custom attributes comparable to shared formulas
We embed and white label Sisense and our premium customers have the ability to author new dashboards with the formulas and attributes we provide. Our users want the ability to create new attributes, comparable to creating a new formulas. Examples: new "Northeast Location" attribute = existing location attribute that we provide where sites = A, B, C new "Shutdown 2023" = existing date field that we provide where date range between X and Y Concatenation of multiple fields to form a new attributes, comparable to Excel new "Is True" type attributes = existing attributes we expose if value(s) = ... Customers want the ability to create their own custom attribute, have then be added to the default values list, in their own "custom" section, where they can search and reuse their own creations. We are a multi-tenant solution provider so tenancy of these custom creation must stay "in tenant" and must do so with us implementing the multi-tenancy feature of Sisense (as we are already deployed and this is not yet robust enough for us to utilize)443Views1like0CommentsRe: Configurable way to dynamically show/hide Simply Ask based on the user
rapidbisupport - Thank you for the idea. This is something we can try! DRay - That is correct. Instead of a dashboard setting, allow it to be more dynamically linked to groups. Our two levels of customers have access to some of the same common "basic" dashboards that we produce. I would like to only expose to this to our premium customers. We can try the dashboard script but if there were a way to do this, without a script manager or having to control with process, it may result in a more streamlined dev and deployment approach.1.5KViews1like0CommentsExport to Excel from the Table widget (without plugin)
We would like the ability to export table widget data to Excel. While CSV is supported, we have had customer complaints because they format in the CSV file and forget to save as Excel, losing the work they've done. We prefer this is a Sisense feature over use of a plugin as plugins require additional operational overhead to maintain and upgrade.1.3KViews9likes4CommentsConfigurable way to dynamically show/hide Simply Ask based on the user
We create a basic set of pre-built dashboards that we publish, where business users can view but not modify. We also have two-tiers of analytics offering for business users (standard and premium). On our common, pre-built dashboards, which are available to both standard and premium, we would like the ability to expose Simply Ask to only those users of premium (hiding it from those who are standard). While this may be achievable via a 2-model, 2-dashbaord set approach, we desire to manage a single set of dashbaords and model to simplify deployment overhead and maintenance.1.6KViews2likes5Comments