Skip to main content

Hi folks,

Getting desperate for some solutions and thought I would crowd source to see if any of you had this issue and had resolved. We all know that the last release had some changes that required MS Admins to approve permission for the Gainsight Outlook App. That worked like a charm for most of our Users. 

 

However, I have 4 Users that we cannot get to make a connection with the app. Out CIT has uninstalled Outlook and the App, validated all the versions and we are having no luck with these users. It isn’t even connecting enough to get to a screen where they could sign on. 

My low tech skills tell me this isn’t an App Issue , but probably something specific to their network credentials , but we are at a loss and they are weeks behind in being able to log emails. 

Dropped this in the GGA Slack community -- hopefully that’ll get you some answers! 😀

Amazing, thanks for that!

If you aren’t in the Slack community yet (can join with your personal email), I highly recommend it. The #quickhelp channel is fantastic. https://join.slack.com/t/globalgainsightadmins/shared_invite/zt-2bm3a4q8h-Spjxc~pI4tpe5wMHTASgpA

​@dayn.johnson  firing up my personal laptop now ! Thanks for the nudge.

​@im4tide Did you find a resolution to this? Having the same issue with one end-user. I also searched Slack but did not find anything.

​@sue.noblette  We really did not. Our CIT had a similar instance occur with an Non Gainsight app and through that process they felt like it was a possible keychain issue with our MACs. He is about to wipe the systems and set them up again 😥.  You can imagine how not thrilled our users are.

Hi ​@im4tide, thanks for starting this conversation! 
Would you be able to help elaborate on “the last release had some changes that required MS Admins to approve permission for the Gainsight Outlook App?” 

We had already received approval within our company to use this a few years back, however it’s back to requesting approval again. 

Is it just going through the same process again? 

Hi ​@jennh  This may point you in the right direction.

 It was a super quick fix , once we knew what the problem was and tracked down an Admin.

Terms & ConditionsCookie settingsAccessibility statement