Skip to main content

    Idea Pipeline

    Filter by idea status

    Filter by product area

    6162 Ideas

    meera.rContributor ⭐️

    Request for Version Control and History Tracking in GainsightNew Idea

    We request the implementation of comprehensive version control and history tracking features in Gainsight to enhance collaboration, accountability, and audit capabilities for our team.Business JustificationImproved Audit Trail: Enable detailed tracking of who accessed, modified, or viewed specific rules and configurations. Team Collaboration: Facilitate multiple team members working on the same instance without conflict. Change Management: Provide visibility into what changes were made, when, and by whom Risk Mitigation: Ability to revert to previous versions if issues arise Compliance: Support internal governance requirements for system changesEx:     At present we can see only the latest last modified name and we don’t see who all modified the rule and how many times it got modified.Requested FeaturesDetailed User Activity Logging: Track who opened, viewed, or modified rules/configurations Timestamp all actions Record specific changes made in each session Version History: Maintain sequential versions of all configurations Display side-by-side comparisons between versions Allow rollback to previous versions Change Attribution: Clearly identify which team member made specific changes Include comments/notes field for change justification Notifications: Alert team members when critical components are modified Provide summary reports of changes made during specific timeframes Expected BenefitsReduced troubleshooting time when issues occur Increased accountability across the team Better coordination of work efforts Simplified compliance reporting Decreased risk of unintended configuration changes

    meera.rContributor ⭐️

    New Feature for CTA, Success Plan Migration from R360 to C360New Idea

    I wanted to submit a feature request that I believe would benefit both Gainsight customers and internal teams by reducing the need for support/services intervention for these types of migrations.Current Challenge:Migration of Success Plans, CTAs, and key reports from R360 to C360 requires Gainsight Support/Professional Services assistance No self-service option exists for administrators to manage these critical data operations Lack of automated roll-up capabilities from child nodes to parent/C360 levelProposed Solution:We recommend implementing self-service capabilities that would allow administrators to:Configure and execute migrations of Success Plans, CTAs, and key reports between R360 and C360 entities Manage roll-up of data from child nodes to parent/C360 level Merge Relationships under a company (similar to existing Company merging functionality)Business Benefits:Improved operational efficiency through self-service capabilities Enhanced data integrity and audit compliance Better management of historical data during relationship deprecation Reduced dependency on Support/Professional Services resources Streamlined customer relationship managementThis enhancement would significantly improve our ability to manage customer data effectively while reducing the operational overhead for both customers and Gainsight teams. It would also align with Gainsight's commitment to providing robust self-service capabilities to administrators.

    rschlette
    rschletteExpert ⭐️

    Enable Dashboard and Report Sharing for Pending PX UsersNew Idea

    Current StateNewly provisioned PX users who have not yet logged in (status = Pending) cannot be included in user-based sharing for dashboards and reports. Sharing options are limited to “Public,” which creates one of two issues:Low trust: Dashboards must be publicly editable, exposing them to unintended changes. Poor first experience: Pending users see no shared assets when they log in, reducing perceived value.Example ScenarioA CS leader wants to use PX to view adoption data. A dashboard exists for them, and ideally, they log in and simply filter by any customer ID in their book of business. Today, this is not possible because:To filter a shared dashboard, users need Edit permission. Direct sharing requires the user to be Active, so we cannot share dashboards or reports until they log in and change status from Pending to Active, unless we settle for completely open public write/edit access.Current WorkaroundsMake dashboards Public with write access for all users (low trust). Ask the user to log in, confirm, then manually share dashboards/reports (awkward and inefficient).Business ImpactEveryone’s org is different, but in most of them you get one shot to demonstrate value. In the current state, a new user either logs in to find dashboards that are constantly open to public changes (so low trust), or an initial user experience that literally does not provide them with any value (no shared assets to view) Please allow Dashboard and Report sharing for Pending PX users so we can have productive first sessions with our largest PX user group