Make it possible that user can change their usernames by themselves

​@Saymon Very interested in this. How do you envision implementing the auto-register?

​@Jef Vanlaer this is already possible with SSO enabled. Basically if a user is logged in our product, a web-app in our case, and they transition to community via a link inside the app which will be an auth link, Gainsight will get the data it needs, I think email, username and ID or something like that, and auto-register the user. This way the user is already logged in when they are in Community. It’s quite common in very large communities.

We’re looking to implement this soon! 

It’s mind-boggling to me that this is not an option! How has this been open for more than 4 years! Come on! This is basic user functionality. ​@Gainsight CC Team 

We don’t support this yet but this idea is valid and we will continue to explore.

Adding my voice to the choir here. We are mid-migration from another platform to CC, and had to make some quick decisions about names to avoid sharing PII. I’m expecting big waves of requests to update users’ usernames once we go live, since we had to change their original usernames quite a bit. I was under the impression they would be able to update them on their own. 

We've made a special topic in our Community where users can request username changes. It's a little over 3 years old and has 290 comments. Half of which, give or take, is my team confirming the change. So about 145 username change requests in three years.

It would be useful if users could do this themselves. But, I would like this option, if it comes, to be locked behind a custom permission. Because we also have some users who would delight in changing their username a lot, and potentially confusing other users. 

Also, it would need to adhere to blocking rules, so we can set words that users are not allowed to have in their userame.

Thanks everyone for the continued feedback and detailed use cases here—we can see this is an important ask, especially for customers managing identity across SSO systems and evolving privacy needs.

Today, usernames in the platform are admin-controlled only. This is intentional, as usernames are tied to identity consistency across the system (e.g., mentions, audit history, and moderation workflows).

What we will explore

• Introducing a separate “display name” field that users can update themselves, while keeping a stable system username behind the scenes.

let me know what you all think about it

Oh, that would be ideal. I love this idea, ​@deepan!

That would be a workable solution for us ​@deepan! 

That would work 👍🏼

A concern for us is user anonymity in a competitive SaaS space, users want to be sure they can remain anonymous.