In the short term, if you want to email me at support@ with the details, I'll fix these manually. We've rarely seen this request and the cost to build this self-serve, even if it didn't have product issues, is greater than the cost to manually fix all known cases for now. I'll build some kind of self-serve solution at the point when I get tired of doing them manually.

I'm going to merge the rest of this into T4104, which discusses "suggest an edit". I'm hesitant to build "make an edit" (vs "suggest an edit") into the product in the general case because it runs counter to other policy behavior. In particular, T4104 discusses a specific case of a hypothetical "phone number" field -- which users and administrators would both have an interest in editing -- interacting with SMS MFA, which administrators should not have influence over.

A social workaround is to change their username to be egregiously misspelled ("epriestley" -> "eeprohestlly") as a penalty until they correct the spelling of their real name. This won't break auth, and I'm quite certain everyone would find this hilarious and it would have no negative consequences whatsoever.

In the Phacility SAAS case we might build a web frontend to bin/accountadmin (i.e., provide you a more powerful, policy-bypassing administrative console as part of the instance management toolset) but I'd like to see wider interest/applicability first, and build better EditEngine/Transaction support into user profile edits than they have today so these edits are more auditable.