Ability to merge 2 accounts into 1 from Control

Woah, you’re on fire Greg! I’m impressed! XD

Major usecase…. relieves us from Huge data cleanup projects.

Totally agree with you, there are some really good use cases that I also experienced multiple times in my life as a Community Manager. When colleagues are leaving and the community still mentions them, I might never notice it and miss out on what could be a valuable conversation...

I know that our recent improvement to create articles in another users’ name has been a milestone on our way to such a functionality - basically we needed to build a logic that allows other users to continue receiving notifications for / being displayed as the author of content that a user originally not has created. Having this dynamic in our platform is what enables us in the first place to allow us to even think about such a feature.

From what I remember from internal conversations, this is something that the product team also had already on their radar while developing. I don't think that there is a set roadmap item for this improvement in the next three months, but having this idea here will hopefully help to prioritize it accordingly!

Thanks for the context @Julian I have to say I am really enjoying the feeling of transparency the ideation product updates/ feedback provides on InSided. Makes me want to hear from a developer/ product manager perspective, what are the pros and cons of this transparent (at least partially) approach as opposed to a private feedback gathering and prioritisation.

Actually thats a great conversation if I can get some  feedback, albeit just from InSided developers/ product managers!

Hi @SmartlyGreg, thanks for submitting this idea! The value of such a feature is unquestionable and there are lots of use cases that would benefit from such a functionality, especially for the community teams' effort put into cleaning and repurposing content but also the effect on the community members.

As Julian mentioned above, the functionality to merge users or transferring ownership of content associated with a user is on our radar, although without a specific timeframe yet. I’ll be following this idea and hope to give you an update on this later.

Thanks for the context @Julian I have to say I am really enjoying the feeling of transparency the ideation product updates/ feedback provides on InSided. Makes me want to hear from a developer/ product manager perspective, what are the pros and cons of this transparent (at least partially) approach as opposed to a private feedback gathering and prioritisation.

Actually thats a great conversation if I can get some  feedback, albeit just from InSided developers/ product managers!`

Regarding your latest comment, around the pros and cons of the transparent approach, the inSided product team learned from the inSpired community that regular and transparent communication builds trust with our customers and sharing the thinking behind accepting or rejecting an idea is received as valuable by customers. Having customers build on (or sometimes even challenge) each others’ ideas is something really valuable that we cannot replicate in a closed environment. Also, closing the loop publicly in our product updates and mentioning which ideas we delivered on, really emphasises that we value our customers’ ideas and are keen to deliver on those. 

For the cons, it's quite tricky to handle timeframe estimation and not committing to delivering features as roadmaps are fluid, priorities changes and technical complexity can always arise. Probably over-communicating can be the antidote of the cons, but it is good to always be mindful of bringing the customer along the thinking path, while not creating expectations that are hard to match.

Big +1 from us :) 

Hello all,
any news on merging users? 

Another use case (SSO login): Even if a user does not change companies, user might get a new email on his/her company side (for different reasons), then registers with this new email (unbeknownst to community admins) and then exists twice.
Thanks!

Has this been addressed? We have so many people with multiple accounts from changing jobs. That’s not ideal by any means… any work arounds?

Definitely want/need this!

This would be EXTREMELY valuable for our organization to have a way to merge profiles. People get new Auth0s which create them new profiles or people change organizations and want to keep their old profile they have contributed toward for years.
This would be huge and other platform providers have a way to accomplish this.

yesssssssssssssss

Chiming in here as well. We just this week had another instance where this would be helpful. This exact thing again: 

Thank you!

As now we have not heard much feedback. so parking this idea for now. we will reopen we get more feedbacks

​@deepan I fully respect Gainsight’s ownership over its own roadmap and that you can’t do everything customers request. However, can you share what you mean by “we have not heard much feedback?” It seems to me that the discussion on this post keeps popping up, and has picked up a lot over the last year, with people saying this would be a major improvement. At one point early on, a Gainsight team member even chimed in to affirm the importance of the use case.

I’m sure others on this thread would be happy to share more feedback if additional specific information would be helpful for Gainsight. Are there questions the team has that we can respond to?

Thanks for the update either way!

Yes! 

Is it possible to merge via API in the meantime?

​@deepan this is functionality that needs to be on your platform. Your competitors (Higher Logic/Vanilla) have this and have had has had this for 5 years. There has been a lot of feedback on this and upvotes. Taking a quick look, this is one of the most upvoted feature requests on the CC platform.

Why is this getting tabled? 

Thanks for the continued engagement and for bring this up — we understand the importance of being able to merge accounts and the impact this gap is causing.

This is an area we will actively start evaluating, given the complexity around data integrity and identity management. At this moment, We are discussing internal regarding the technical feasibility . I will get back to you all for inputs on this thread while we complete our internal assessment.

I will come back with a clear update once we have more to share. Right now we are working on other big releases stay tuned to get more updates

Appreciate your patience.