Skip to main content
gunjanm
Expert ⭐️
September 20, 2021
Open

Auto Unfollow Notification Settings

Related products:CS C360 & R360 & P360
  • September 20, 2021
  • 25 replies
  • 597 views

Love the auto-subscription feature based on role assignment on Company and/or Relationship records as detailed here: https://support.gainsight.com/Gainsight_NXT/Notifications/Admin_Guides/Admin_Notification_Settings#Configuring_Auto-Subscription_for_Notifications 

However, when someone is unassigned from, say, the CSM user lookup on a Company, they are not automatically unfollowed from the Company. That’s not fun. Let’s fix that please. 

 

Collating requirements from @Elana Cipin’s idea before merging the two:

(1) Have ability to report on what Companies you are following (I understand this might be available in SFDC, but not NXT).

(2) Have ability as an admin to Mass unfollow

 

25 replies

Contributor ⭐️⭐️⭐️
January 7, 2025

I would also like to know the status of this as my org is facing some similar issues as described by Elana today. Not being able to mass-unfollow companies is causing so much extra work that would be better spent doing just about anything else.

ebell
Gainsight Employee ⭐️
Gainsight Employee ⭐️
March 18, 2025

Hey Gainsight Communities!

 

I also wanted to chime in as a Gainster on behalf of a customer. This is a priority for the customer because they use Company Teams, and this allows them to unassign a CSM from an account, completely removing access for that CSM (including C360, complete data restriction). 

The problem comes in when the CSM had been subscribed (+Follow) to the Company and later was unassign from the Company. 

When this happens, the CSM is still receiving updates for that Company even though they have been unassigned. They can’t even access the C360 to Unfollow from updates to this company.

As a workaround, the admin had to temporarily give that User back access to the Company, then log in as the User and unfollow the Company. 

The customer is also concerned that the former CSM is getting information that they shouldn’t have, which is why we would like this prioritized.

Thank you,

Emily Bell, Sr. Enterprise Technical Support Analyst
ssamarth
Gainsight Employee ⭐️
Gainsight Employee ⭐️
April 17, 2025

@ebell I understand the frustration. There’s no specific update at this time, but we plan to evaluate this in the second half of the year

ssamarth
Gainsight Employee ⭐️
Gainsight Employee ⭐️
June 8, 2026

Hi everyone,

Thank you for all the feedback and patience on this thread. We're evaluating this area and would love your input on a few specific scenarios before we finalise our approach:

Q1 — Handling existing stale follows If we were to automatically clean up follows where the user is no longer assigned to that account  would you want that to cover only follows that were originally set via auto-subscribe, or all stale follows including ones users set manually? Would a blanket cleanup cause any unintended side effects in your org?

Q2 — Auto-follow when added to a Company Team Beyond role-based lookup fields (e.g. CSM on a Company), would it be useful if a user automatically followed a company when they were added to its Company Team  and unfollowed when removed?

Q3 — User-level follow management If admins get the ability to view and mass-unfollow on behalf of users  do you still see a need for individual users to have their own view of all companies they follow, with the ability to unfollow themselves? Or does admin control cover the need sufficiently?

Q4 — Reporting on follow/subscription data Would it be really useful to have the User Subscription data (who follows which company) exposed as a reportable object in Gainsight — so you can build reports . What would you use it for if admins get a separate capability to do bulk unfollow.

Q5 — Rules Engine for follow management Given that auto-follow and auto-unfollow based on lookup fields would handle most assignment-driven scenarios — do you see a need to trigger follow/unfollow actions via Rules Engine as well? If yes, what use case would that cover that the lookup-field config wouldn't?

Would love to hear how these scenarios map to your day-to-day. The more specific you can be, the more it helps us prioritise.

Helper ⭐️
June 11, 2026

We use a combination of Company Teams/Relationship Teams for our team assignments. So Q3 is most relevant approach for auto follow and unfollow along with user level filters within the Company/Relationship Teams giving us flexibility to auto subscribe specific personas. 

 

For LT and Mngrs personas Q4 option that suggests reporting with inline edit would be handy manage their subscriptions and could extend to other personas as well.

 

Q5 option is also a great extension to handle any anomalies in case of reassignments that falls through the cracks or periodic bulk updates