Hi all
Referencing this question:
And because:
- [SPOILET ALERT]: we can’t force update Gainsight Home
- Identifying the rogue users is overly cumbersome
- Asking support to force remove dependencies is really a waste of Support’s resources
- In what universe did it:
- Make sense for inactive users to create dependencies on Gainsight Home (especially where we can’t delete such users)?
- 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!
- 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:
- Admins must be able to force updates to our chosen users, groups of users or all users at any time.
- 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)
noun1 : 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