Skip to main content

    Idea Pipeline

    Filter by idea status

    Filter by product area

    6037 Ideas

    bjoern_schulze
    bjoern_schulzeHelper ⭐️⭐️⭐️

    Privacy / Data erasure policy: Fully remove a username from the community after account removalParked

    inSided stated in their data erasure policy that when a user account is being removed - in order to anonymize a user:“no personal data is available anymore, nor in the system nor in any backup - the user record can no longer be retrieved” “their content will be left intact to avoid damage to the community - but the attached user record is now Anonymized”But unfortunately that’s not fully true. What happens:A user (in this case “Spreeandre”) registers in the community, posts topics and / or comments Other users interact with this user by quoting or mentioning them The user then asks for his account to be deleted After the account is deleted, the user’s own content is being anonymized But: The username in mentions and quotes won’t be anonymized → inSided’s claim that “no personal data is available anymore” isn’t true because it is still easily possible to connect the anonymized content to the original username (which can easily be found via Google)The reason why this happens is:The username is being inserted as a plain text so after a posting was published, the username is a fix part of the content The correct way of doing it would be to load the username from the database every time the content is being loaded → So when a change is being made (e.g. username change or user is being removed), the data will be loaded from the database and instead of the plain text username the updated “Anonymous” (or changed username) will be displayedThat’s why our proposal is:In order to really ensure the “right to be forgotten”, it is necessary to change the way the usernames are being displayed in mentions and quotes. It is necessary to pull the data from the database instead of inserting usernames in plain text.If this isn’t done, inSided customers are violating the GDPR because they don’t fully remove the identifiable user data from the platform automatically (and doing it manually by editing every single piece of content where an anonymized user was being mentioned or quoted is a very time-consuming and error-prone work around).

    spencer_engel
    spencer_engelExpert ⭐️

    Allow SFDC Contacts to be the source of truth in Gainsight instead of Company Person/PersonNew Idea

    I find myself spending a lot of time architecting our Company Person model in such a way that will optimize what our system. The problem, though, is there has never really been a perfect - or even decent - blueprint as to how to do this, especially for customers like us (and my previous org) who use the Account Contact Relationship object. Plus, Gainsight’s arcane “Load to People” action makes updating/upserting to Company Person even harder than it already is, as I’ve already outlined below.  Here are just a few of the common issues I’m constantly playing whack-a-mole with: Duplicate and orphaned records: Contacts that exist in Salesforce but don't cleanly map to a Company Person, or Person records that linger in Gainsight long after they've been deactivated or deleted in Salesforce. Sync headaches: Field mapping mismatches, sync failures, and contacts that show up in one system but not the other. Admin overhead: Time spent building and maintaining rules, connector jobs, and data management plays just to keep contacts in a usable state. End-user confusion: CSMs logging Timeline activities to stale contacts because the Person model hasn't caught up with what Salesforce already knows. I presume the initial intent behind the Person object was to make Gainsight CRM-agnostic, which I understand. But let’s be realistic here - we know Salesforce still is the predominant CRM, which is reflected in the fact its related list functionality, connectors, etc. are all much more well-developed and high-functioning than other CRM competitors. So why not acknowledge this by allowing Salesforce contacts to be the source of truth for Timeline activities, JO Programs, and more if admins so choose? This would presumably have the added benefit for Gainsight of deflecting a lot of support tickets and cleaner customer data.  The bottom line is contact cleanliness is already a difficult issue for pretty much every business. Forcing customers to use the Person/Company Person model compounds the problem.

    t.nelsonContributor ⭐️

    Allow "Associated Persons" to be displayed as a column in Cockpit admin defined viewsNew Idea

    We utilize the Associated Persons feature in Cockpit and see a lot of value in associating the relevant customer contact(s) to a CTA. However, one key limitation is that Associated Persons cannot be displayed as a column in Admin Defined Views.Today, a CSM must open each CTA to see who the CTA is associated with. For organizations that create person-centric CTAs (such as onboarding contacts, low usage users, champions, or executive sponsors), this adds unnecessary clicks and makes it more difficult to prioritize work.It would be extremely valuable if Gainsight allowed Associated Persons to be selected as a column in Cockpit Admin Defined Views.Potential benefits:Allow CSMs to immediately identify which customer contact a CTA relates to. Improve efficiency by reducing the need to open CTAs just to identify the associated person. Increase adoption of the Associated Persons feature by making the information visible where CSMs spend most of their time. Better support person-centric workflows such as onboarding, adoption, renewals, and dormant user outreach.Possible enhancements:Display the primary associated person by default. If multiple people are associated, display the first person's name followed by "+X more" (for example, John Smith +2). Allow filtering and sorting by Associated Person within Cockpit views.As Gainsight continues to expand person-centric capabilities, surfacing Associated Persons directly in Cockpit would make the feature significantly more useful for day-to-day CSM workflows.