Skip to main content

    Idea Pipeline

    Filter by idea status

    Filter by product area

    6159 Ideas

    Kritika Karir
    Kritika KarirContributor ⭐️

    Feature Request: Ability to Hide/Restrict Entire Community Sections & Expose Hidden Status via APINew Idea

    Objective / SummaryCurrently, community admins can only hide individual categories, not entire sections. Additionally, the community APIs lack a parameter to indicate whether a category or section is hidden. We need the ability to completely hide or role-restrict entire sections in the UI, alongside API support that accurately reflects these visibility states.The Problem Administrative Overhead (UI): When we need to retire or temporarily hide an entire section, we are forced to manually drill down and hide every single category within that section one by one. This is tedious and inefficient. Data Inconsistency (API): Because the API does not return a "hidden" status parameter for categories or sections, there is a major discrepancy between what is configured in the backend and what the API pulls. This breaks custom integrations or external dashboards that rely on accurate content architecture. Proposed Solution Section-Level Controls: Add an option in the community backend to completely hide an entire section or restrict its visibility to specific user roles with a single toggle. API Visibility Parameters: Update the API payload to include a boolean parameter (e.g., "isHidden": true/false) for both sections and categories so external applications can respect the backend configurations. Business Value / Impact Efficiency: Saves administrative time when archiving content, restructuring the community, or managing seasonal/beta sections. Data Integrity: Fixes the inconsistency between backend configurations and API outputs, allowing developers to build reliable, seamless custom community experiences.

    LizzieContributor ⭐️⭐️⭐️

    Watchparty / live chat functionality in eventsOpen

    Hello everyone, We have several key product events that happen throughout the year. These are great ways to bring our community together to watch the live event and enable members to provide instant commentary, as well as speak more casually to other members.  Currently this is very hard to do, we share the live stream (usually a Youtube embedded video) in the community post or in the event page. But, without refreshing the page each time there is comment and scrolling to re-find your place, it is hard to keep the conversation alive.  It would be fantastic to have more capabilities within Events (and possibly other boards), enabling the ability to build something that can then encourage more conversation after the event (as well as before).  I’d like to see the live stream video, and the comments on the side (open to other ideas), but this prevents having to keep scrolling to the top of the thread list to watch the video.  In addition, the option to add polls (with the ability to make them anonymous or only who has responded visible to admins), surveys or highlight questions throughout the event would be also be helpful (especially if you are trying to gauge how well the announcements are going or alternative if a question is popular).  If you are also looking for something similar or have any current workarounds please do share, I’d love to hear any idea. Thanks so much. 

    pfpsimoesContributor ⭐️

    Timeline - Bulk Update of Associated RecordsNew Idea

    Problem StatementCurrently, updating associated records (such as Contacts/Attendees or related records like CTAs) on Gainsight Timeline activities must be done individually. When a CSM needs to clean up data, link multiple historical meetings or emails to a newly created CTA, or update associations after an account transition, they have to manually open each Timeline entry. This process is highly tedious, time-consuming, and acts as a barrier to maintaining clean data hygiene. Proposed SolutionIntroduce a multi-select checkbox capability directly in the Timeline list view, accompanied by a bulk action toolbar. Multi-Select Functionality: Allow users to check multiple Timeline entries simultaneously from the main view. Bulk Action Menu: Provide a "Manage Associations" or "Bulk Update" button once multiple entries are selected. Association Modal: Open a modal that allows users to: Add a specific record e.g., link a single CTA or Contact/Attendee to all selected activities. Remove an existing association across the selected entries. Replace a current association with a new one Business Value & Impact Massive Time Savings: Reduces administrative overhead for front-line CSMs, freeing up hours previously spent on manual data entry. Improved Data Hygiene: Encourages accurate data tracking by making it frictionless to link Timeline activities to relevant Gainsight objects. Enhanced Reporting Accuracy: Ensures that CTAs, Success Plans, and Opportunities reflect a complete, accurate history of customer interactions, leading to more reliable executive reporting and healthier customer health scores.

    darkknight
    darkknightExpert ⭐️

    CS: X-ORG 2.0 - Admins need ability to deselect dependenciesNew Idea

    I don’t know if there is an idea out here for this already or not, but admins need the ability to deselect dependencies when creating an X-Org 2.0 migration bundle because the scope of the default dependency generator is too broad. As an example, I created two Playbooks associated with a single CTA Type and two Success Plan templates associated with a single Success Plan template. Nothing wild, no custom fields, or anything.The Migration tool identifies 128 dependencies including CTA Types and Success Plan Types that are unrelated to any of these that I am attempting to migrate (including ones that are INACTIVE in my sandbox), in addition to other fields under Company, Call to Action, Task, etc. that did not require/have any changes made to them as part of the generation of these assets. I understand Gainsight is trying to ensure that any dependent assets that may be different/have been adjusted as part of the process are carried over, but this control needs to be given to the admin to determine which dependencies are relevant and which aren’t.For many of us, our Sandboxes are not necessarily 1:1 matches to Production.  We often use them as “scratch pads” for testing new features, processes, etc so some of the dependencies the migration tool automatically selects could contain values/components that are not intended for promotion to production.We need more granular control over it. --------Success Plan Template I’m trying to migrate, under the “Extend Product Onboarding” Success Plan type: Migration dependencies include irrelevant SP Types: Including ones that are deactivated:Which it does attempt to insert, since it does not exist in my Production environment:  And then attempted updates/insertions to DA Picklists which the logs don’t even define to which picklist they are related to forcing me to try and deduce it but also are either not different between Sandbox and Production and is unclear why they are attempting to update OR are, again, values related to deactivated assets:  

    t.nelsonContributor ⭐️

    Enhance the Home Page Calendar Widget: Expanded History & Configurable Company AssignmentNew Idea

    I'd like to suggest two enhancements to the Home Page Calendar widget that would improve usability and data consistency for administrators.1. Extend Calendar History Beyond the Rolling One-Month WindowCurrently, the calendar only allows users to navigate back approximately one month. It would be helpful to allow users to access older meetings directly from the calendar widget without relying on other navigation methods. This would make it much easier to review historical customer interactions, update meeting records, and perform administrative tasks for meetings that occurred more than a month ago.2. Allow Administrators to Configure the Default Company AssignmentToday, the calendar assigns the Company on a meeting based on its current default logic. We'd like administrators to have the ability to configure this behavior so the default Company is the Company associated with the Person on the meeting.This is especially important for organizations using the Gong connector. Gong meeting synchronization depends on the Company assignment being consistent across both platforms. When the Calendar widget assigns a different Company than Gong, it can create inconsistencies that require manual correction and complicate reporting and meeting management.Giving administrators control over the default Company assignment would: Reduce manual cleanup after meetings are logged. Improve consistency between Gainsight and Gong. Increase confidence in meeting-related reporting and customer activity data. Better support organizations with complex account hierarchies or multiple Company records associated with the same contacts. These enhancements would improve both the end-user experience and administrative efficiency for teams that rely heavily on the Home Page Calendar and Gong integration.