Skip to main content
New Idea

Force Update Gainsight Home

Related products:CS Gainsight Home
  • May 5, 2025
  • 3 replies
  • 71 views

alizee
Forum|alt.badge.img+13
  • VIP ⭐️⭐️⭐️⭐️⭐️

Hi all

Referencing this question: 

And because:

  1. [SPOILET ALERT]: we can’t force update Gainsight Home
  2. Identifying the rogue users is overly cumbersome 
  3. Asking support to force remove dependencies is really a waste of Support’s resources
  4. In what universe did it:
    1. Make sense for inactive users to create dependencies on Gainsight Home (especially where we can’t delete such users)?
    2. Make sense for active users to be stuck with old reports and old data → at best, it makes sense for them to decide if they want to see a report or another, but if a report is removed, it must be removed for them as well! 
    3. Make sense to not be able to force update layouts to all users: Notification settings for GS Home | Gainsight Community  (no, logging as them to force update Gainsight Home isn’t an option as figuring out who the rogue users are is cumbersome and chasing them to update is equally not helpful

I’m turning the above question into an idea so we can get the upvotes going (for which I take 0 credit) but it needs to change:

  1. Admins must be able to force updates to our chosen users, groups of users or all users at any time. 
  2. Inactive users, when inactivated, if they have created some dependencies through any form of customization, should be updated in such a way that no dependencies remain. 

 

Because currently, what we’re experiencing is this: 

Gainsight Home | /ˈɡeɪnsaɪt hoʊm/ | (abbr. GS Home)
noun

1 : Where admins must embark on epic quests to remove dependencies from the ghosts of deactivated users.

2 : A feature that traps end-users in a time capsule of potentially outdated data.

 

Thanks

A

3 replies

romihache
Forum|alt.badge.img+9
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • May 5, 2025

I couldn't agree more! The inability to force update Gainsight Home layouts has a tangible impact on our ability to effectively roll out new features and ensure all users are working with the latest information.

The manual effort involved in identifying users on outdated layouts (been there, done that 😖: How to identify who is using a report in a custom Home layout and remove the dependency) and doing the updates ourselves or guiding them through the update process is a significant drain on time and resources for everyone involved.  A direct 'force update' capability and automatically removing the dependency when a user is inactivated would be a significant UX improvement.


sarahmiracle
Forum|alt.badge.img+11
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • May 5, 2025

Situations in which I absolutely need the ability to push a forced update:

  1. We include custom reports for CSMs on NRR. The business decides to change CSM targets and/or reporting for NRR, and I need to remove the report from Home
  2. We refreshed our Home - completely new widgets, reports, KPIs - to reflect changes in our business and our operating model. I need to refresh Home for all CSMs so they see the new experience.

...and many more.


HollySimmons
Forum|alt.badge.img+1
  • Helper ⭐️
  • March 4, 2026

Please make this possible, we cannot remove old fields when someone is on an old version of our which has them included. I’ve just had to manually review which Home users are using, log in as them and update them to the latest version in order to be able to do this. 

We should be able to force an update so users have to use our latest layout.