As an org administrator, I would like to be able to update a username instead of the current workaround which is to create a brand new user and move all content from the old to the new user.
Use cases:
Workaround details from Esri support: http://support.esri.com/en/technical-article/000011984
My organization was recently acquired by another and it would be great to have a way to change the usernames to reflect the new organization without deleting and remaking all the accounts.
The other use for this would be with Enterprise Logins (Single Sign-On). AGOL automatically generates a username consisting of the users email address followed by an underscore and a suffix, but since the email address must be unique already it would be cleaner and easier to remember if the username was just the email address.
I very much support this idea! At the governmental institutions we work with, people in certain positions change often. Still they want personalized user names (understandable) and not the name of a position. All users are also in use so I cannot use the workaround through creating a new user.
I too strongly support this idea. Changing user names is a very requirement within my organization.
Any movement on this Esri - it would be handy.
Also on board with this idea. We've had users get married (or the other way around). Changing the user name would be easier than recreating everything.
I understand why ESRI cannot do this... since each user is used to save data, maps, and apps. Any change in name would break all the links. You can, however, make a new user and use the ArcGIS Online Assistant to transfer over the data, maps, and apps. This process will rewrite the links. Its a pain but is necessary the way the servers act.
The best way would be for a behind the scenes script.
Front end admin sees: `Are you sure you want to change the username?`. If they click yes, the following happens:If user name is changed:
Create new user account in the organization
Change ownership of all existing items
Migrate group ownership and membership
Migrate privileges and licenses
Delete old user account
Yes! And make it easier to delete old accounts, transfer user names and change primary emails. I've had to spend time on the phone with tech support to do all of these things.
Following on from a question asked in the 'ArcGIS Online: Q&A with the Product Team' session at the UC2020; Sentha Sivabalan the idea to change a username has been around since late 2017. Do you know if this is on the current roadmap? Thanks, Jamie.
on the content piece,
maybe with the SSO with SAML or similar options you turn this on its head,
once data is created and put into production for the organization to use,
change ownership on it to match something like AD security groups = Portal/AGOL group,
such as a Portal/AGOL user to be that groups content "Publisher"/"Owner",
then what you see is what you get,
on the name changes piece,
AD/DNS/Portal/AGOL has enough "ghost" type issues already.
just managing the items now can get corrupted without trying to script more low level pointers.
voting up but with an abundance of caution for potential BUG type disastrous results
It sounds like the system uses the username as the primary key.. I wonder if they created the equivalent of a GlobalID and then joined that to username in the backend, could the username then be changed?
On a related note, there was another challenge when I was in emergency management for disaster response. We had a script to generate hundreds of user names (we had an Esri DR agreement). Great functionality and it worked well! We needed it since we couldn't have hundreds of usernames just created and parked indefinitely. It created them on the fly as needed based on people's names. And a lot of people have been and will continue to be there for a long time. So when it creates the name it ends up adding a number, if it already created a username for them last time, since apparently even if a user is deleted it's never really deleted, and you can't re-use the name. During hurricane recovery it was a challenge to track down which number (1, 2, or 3 etc) went after each user's username, when re-issuing everyone login credentials.
Such an easy win this. Get it sorted please
As an administrator I think these enhancements are a must. Our organisations name has changed recently and needs changing (this is currently in the usernames) as well as a few cases of name changes. Having to re-assign all the content, create a new user, re-assign the content to a new user is incredibly cumbersome.
I find it crazy that this post is 5 years old and there is still no movement from Esri to enable administrators of an organisation to do simple username changes.
Please implement this. I had to change my first username today as both their first and last name has changed and was surprised to see that this still isn't possible to do. Luckily, they only had a couple of items and was a straightforward switch, but it could get complicated fast if they had many folders of items and were in lots of groups.
Agree with this and the biggest problem with transferring content which I don't see being mentioned here is with content shared directly with a user directly or external groups they belong to.This means first identifying what content and groups they have been invited to and then chasing the owners or someone with permission to share and asking them to share to the new user name. This is potentially asking clients or suppliers to do work to support our internal administration.
Esri, @KoryKramer , please push this issue to your very intelligent software developers and programmers.
There is no way this should be impossible. My esri user name isn't just tied to AGOL. It is embedded in Esri - my.esri, the community, my organization account, content, settings, who knows where else. I can't just make a new user name and transfer AGOL content.
1) My user name is a security problem - it is my old last name. I don't want that public anymore, shared with the world. It's been 15 years.
2) The AGOL users of my organization are very confused - who is this "xxusername" that created this web map? I have to explain..."that's me. See, Esri doesn't allow me to change my user name so you have no idea who made all of these maps. And therefore, who to go to to request changes and updates." "That's insane", they say.
3) In a culture where the woman is (usually) the one who changes her name upon marriage and sometimes on dissolution of marriage, this strikes me as a sexist policy where "the system" can't allow you to change your user name. Well, let's change the System. (I realize this bullet point might be a bit of a reach, but this is how it feels to me. So I'm willing to bet, I'm not the only one who feels this).
Thank you.
I would second this @KoryKramer.
We live in an era where Operational Security requires password changes every six months. It would seem the user community as a whole would benefit from the added ability to change ArcGIS Online UserNames.
Respectfully Submitted,
Eric
Just fix this
I understand the reasoning as to why this is not currently possible to some degree, but at the same time, it seems like a very important features that should be standard in business environments. While it may not be possible with the way the system is built currently, it should be possible to change the AGOL backend to support this over time (and it has been some time since this was first raised). I don't think it's fair for ESRI to just say we will not address this due to the reasons our system is built, when they are the ones in charge of how the system is built and could change it accordingly.
This would help with a lot of things, like people changing names for"happy" both "sad"and reasons, organizations changing names, organizations changing login schemes (built-in to SAML), typos and mistakes, changing of username generation scheme in organizations, etc.
I see that most of the steps necessary to create a new user with a new name, and migrate old content and groups to the new user, can be automated, but not all. For example, group memberships in external groups cannot be transferred unilaterally from the home org, so this part cannot be automated. This is a big problem for large orgs.
One more vote. Trying to move to SSO/SAML. Autogenerated usernames 40 characters long! Existing user names can't be standardized/updated. Content on AGOL can be migrated to new account, but finding everywhere else - including community.esri.com, support history, my.esri, is problematic
I would like to add an additional vote for this. This is causing the move to Single Sign On to be a bit more finicky and persnickety than it needs to be.
Hello,
Any movement on this?
Thanks,
Matthew
I'm also interested to see if there are any updates on this. I appreciate the ability to add a display name for someone's ESRI profile, but there are a lot of instances where that feature isn't going to be enough.
I am also interested in this.
-Ian
Such a great idea, logged over 7 years ago with nearly 300 kudoses and it's still not implemented. Esri say they look at the Ideas to direct development but this kind of suggests otherwise.
We just submitted a support ticket for this..we have a AD consolidation project going on in our Org. 700 users impacted (coming into larger domain). Manually moving them not a realistic option, tons of content, some to groups with shared editing that makes content transfer challenging etc. AGO should be able to poll SAML for UPN change or allow us to edit manually. Fingers crossed they have a work around!
Yes please, fix this!
Piling on - we have this use case now as well where we need to 'map' Azure AD login to the same naming convention as existing users. It seems like we will have to systematically migrate user content, delete all of our users and have them re-created upon Azure SSO login, and then restore content. This also breaks any collaborations they were invited to. I can't find any other alternative so far.
Sign in to post, follow content, and more. New here? Register for free.
