Skip to main content

    Idea Pipeline

    Filter by idea status

    Filter by product area

    6164 Ideas

    rschlette
    rschletteExpert ⭐️

    Rethink Analytics : Viewer Role-based Permission Set in PXNew Idea

    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)

    sarahmiracle
    sarahmiracleVIP ⭐️⭐️⭐️⭐️⭐️

    Set display options for manual Milestone Type in TimelineNew Idea

    As a Gainsight Admin, if you want to track milestones using Rules Engine, these are “Manual Milestones.” As a Gainsight User, if you want to log a milestone to timeline manually, these are “Manual Milestones.”Issue: Manual Milestone types assumes that 1) the admin needs it for logging to rules engine AND 2) the user needs it to log manually to timeline. Turning “on” a manual milestone automatically makes it visible/accessible to the user in Milestone Type picklist on Timeline.Why this matters: There are milestones that I want to automatically log for my CSMs, and I have to use Manual Milestones for these. However, a CSM should ONLY see milestone types that THEY are responsible for logging to timeline manually. They shouldn’t see the milestones that I’m already automatically logging for them using Rules Engine.User Stories:As a Gainsight User, I only see the Milestone Types that are relevant to me when logging a manual timeline milestone. As a Gainsight Admin, I am able to configure which active Manual Milestone Types are available in Timeline and which are not.Use Case: We use Manual Milestones to automatically log milestones to relieve the administrative burden from our CSMs (eg...Opportunity Stage Change, Risk Identified, Risk Resolved, CSM Sentiment Changed). The only Milestone Type that a CSM user logs themselves is “Verified Outcome Achieved.” Therefore, this should be the only Milestone Type they see when they log this milestone.

    emiller
    emillerHelper ⭐️

    Ability to control sort order of Custom Views in ControlNew Idea

    Apologies if this idea has already been suggested - I tried to search for it but didn’t find one! I use a series of custom views in CC Control for my community management workflows.  I use some views frequently, and others only occasionally.  I would really love some way to change the sort order of these views so I can keep the most recently used at the top. I find myself having to avoid creating new views since it makes it harder to access the ones I need most as the list gets longer.  I tried re-purposing existing views by editing a view that I wanted to keep in the same position on the list, but after renaming the view it was placed in a different, seemingly random position on the list.  If it cannot be done explicitly, it would be really great if these were sorted based on usage, ID, or something we could directly or indirectly control.  Any workarounds would be welcome short of deleting and rebuilding the whole list.  ;-)As an example, here are the views I use today:My Open items - via labels+assigned moderator (this is basically my queue of topics assigned to me, used daily) Moderator queues - labels+assigned moderator (one view for each moderator containing their open items, used as needed) Unassigned open items - labels+unassigned (for auditing, used occasionally) Questions views (Answered, Unanswered - used monthly for metrics) Product Feedback topics I’m tracking - via tags (used monthly for metrics) Escalated topics - via tags (used monthly for metrics) My Closed items - via Labels (for auditing, used as needed)