Skip to main content

Hi All - Does changing a username come with any issues? IE can it stop notifications, break the SSO? 

Employees have complained that they can’t find the coworker they’d like to tag so I’m thinking of implementing a standard naming convention for employees (first initial, last name, etc). I just want to make sure that if I go and change employee usernames, I won’t be breaking anything!

In general, I don’t think that you can’t break anything and I believe it is a good idea to have a standard naming convention for the team. The profiles would still be available, the SSO shouldn’t be affected (as the SSO field usually doesn’t have anything to do with the community username) and the old content would still be linked to the same account (but now under a new user name).

The only downside (I consider it kind of a bug and even a potential data privacy issue) is the quote function. If you ask inSided to rename your username from “Kgastaldo” to “Mynewusername” today, then all existing quotes of your content will still be shown as “Kgastaldo wrote”. It won’t retroactively change the name to “Mynewusername wrote”.

But even with this in mind, I’d say: Go for it.


@Kgastaldo thank you for asking out loud here and @bjoern_schulze for adding in that ‘quote’ usecase; so do we know IRL that nothing broke, right?


Changing usernames is a daily occurence in a lot of public facing inSided communities (e.g. if a user name is breaking community rules). There aren’t any known instances when anything “broke”.


I can added that I’ve updated plenty myself and have had no issues. 

 

But I’m looking at a mass update to some usernames and was glad this thread was here to alleviate some concerns. :) 


Reply