Gainsight PX dashboards allow us to surface important adoption details on reports like Funnels and Retention analysis that can not be shared through CS integration, or easily recreated in CS reporting. In order to provide access to PX dashboards, we use the Role-Based access controls in User Management.
Most commonly, we deploy Analytics:Viewer permission to allow users to view dashboards. Intuition would tell us that this permission set is a read-only role, but that is not the case. As documented, the Analytics:Viewer permission includes user permission to “create dashboards”. I understand that allows users to clone and customize PX dashboards, but it also creates a big change management problem in our organization’s PX tenant.
The problem: if users create dashboards (clones or new dashboards), they can create PX dependencies in reports and filters, including user and account attributes, and product mapper features. So if we have a few dozen users with the lowest level Analytics permissions, called ‘Viewer’, they all have the ability to create a network of dependencies that block and delay changes to the User and Account objects, as well as the product mapper. It’s important to note that PX Admins can not resolve these dependencies, and are required to either contact each PX user and request that they be resolved individually, or contact support to have them resolved.
The ask (1 AND 2) OR 3:
- make the Analytics:Viewer permission truly read-only
- use the currently unused Analytics:Editor permission to extend Viewer permission to include ‘create dashboards’, OR
- allow Full Admin users in PX to resolve/remove any dependency (e.g. admin users can not currently delete a product mapper feature that an Analytics:Viewer user has in a dashboard filter. They have to find that user and request they make the change to the filter)