Skip to main content
New Idea

Issue when updating notification preferences when adjusting for NXT or SFDC Hybrid Preferred Notifications

Related products:None
jean.nairon
katie_b
heather_hansen
darkknight
gunjanm
+6
  • jean.nairon
    jean.nairon
  • katie_b
    katie_b
  • heather_hansen
    heather_hansen
  • darkknight
    darkknight
  • gunjanm
    gunjanm
  • bradley
    bradley
  • sarahmiracle
    sarahmiracle
  • rho_ran_experian
    rho_ran_experian
  • kyeh
    kyeh
  • mcbarthi
  • alliheller

sarahmiracle

I received a Slack message from a new user the other day telling me that she received an email notification about a new CTA that had been assigned to her, and when she clicked the link to take her to the CTA, she received an error message.

She shared the error message with me, and I could tell that the link was directing her to log in through the SFDC Hybrid Gainsight managed package. While we sync users to Gainsight using the SFDC User Connector, our users work out of NXT and not SFDC. Many of them don’t even have the permissions to use the NXT managed package.

The first problem here is that because we are syncing in users from SFDC, it is defaulting notification preferences to SFDC hybrid. I don’t want that, and it means I’ll need to reactively update any new users’ preferences to set to NXT.

Now the second problem, is that I know a user can make these changes for themselves, however they need to do so from within SFDC Hybrid. Because my users do not have permissions to use NXT in SFDC, they aren’t actually able to update their own permissions.

Then the third problem comes in when I tried to mass update all of my users. It has been some time since I’ve checked my new users’ notification preferences, and I figured it was just a good idea to set all my users in bulk to NXT as their preferred for notifications. 

I followed the steps in the help article, but then I noticed odd behavior. Here’s what happened:

  • Navigated to User Management > changed source to SFDC
  • Clicked the box at the top of the user list to select all in the page view
  • Then clicked the box that said “Check all 77 users” (so that I could choose all users, not just the 25 in my page view)
  • Clicked the three dot menu to change notification preferences
  • Received the message below telling me that 25 users would be changed even though 77 were selected

 

As a workaround, I needed to change my pagination to view 100 records on a page, then select all, then update preferences.

 

This post is to request that:

  1. We allow admins to determine the default preferred notification setting for all users regardless of how the user was synced into Gainsight
  2. We allow users to change their settings natively within Gainsight NXT
  3. We fix the bug experienced when trying to bulk-update user notification settings preferences

4 replies

bradley
Forum|alt.badge.img+7
  • Expert ⭐️
  • 1127 replies
  • July 26, 2022

Agree that this is super clunky execution of a fix that appears to address this: 

which is still marked as planned. Maybe this is just phase one and it will be marked as implemented once the bugs are out? :)


anirbandutta
Forum|alt.badge.img+2
  • Expert ⭐️
  • 1804 replies
  • July 28, 2022

Converted this to an Idea.


ssamarth
Forum|alt.badge.img+1
  • Gainsight Employee ⭐️
  • 164 replies
  • August 10, 2022

@Neha Gupta Looping Neha to take action on bug highlighted above.

@sarahmiracle Will look into the ideas suggested by you. Thanks


kyeh
Forum|alt.badge.img+5
  • Gainsight Employee ⭐️
  • 4 replies
  • May 22, 2024

@Neha Gupta @ssamarth checking if we’ve made any headway on this issue. My customer needs to also adjust notification settings but for 2000+ users. Changing show 100 records on a page isn’t going to work for them. We are not able to make the update in 1 step but at best repeat the process 20+ times. How can we ensure we’re adjusting the notification for every user with confidence given this current blocker?


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings