When provisioning a new user, do you ask the user’s naming preference or do you stick to a set standard? Example, if there’s an Elizabeth Grey who goes by Beth, do you go with bgrey@domain or egrey@domain.
When provisioning a new user, do you ask the user’s naming preference or do you stick to a standard?
Or a long hyphenated last name, do you include both last names or do you ask the user?
Open Thread in Slack
Our convention sticks to a firstname.lastname format, but allows the employee to state if they have a preferred name they would rather use in place of those. So for your example, we would mark down their legal name as Elizabeth Grey (if you need that for anything), but their email would be bgrey@ and display names would be Beth Grey.
Open Thread in Slack
Userlevel 3
+2
- Active Member / Beta Tester
- 1390 replies
-
20 January 2021
Userlevel 1
+1
- Active Member / Beta Tester
- 127 replies
-
20 January 2021
Same as
Open Thread in Slack
We ask in a new hire form but its a manual process to check that their email choice is valid and input the email
Open Thread in Slack
in a past company we had a formula creating emails from abbreviating the first + last name and it accidentally created one that was profane and the employee and manager were not happy. I ended up adding a 'badwords' list to java code that made users. It was one of my favorite git commits ever getting to add a list of so so many bad words to github.
Open Thread in Slack
Userlevel 3
+3
Same.. our HR teams will confirm a preferred name into our HRIS (which then flows to IDP, and as soon as Bettercloud gets its hands on it, all the accounts get created). We emphasize hard that HR (recruiters) need to get this info correct the first time.
Open Thread in Slack
Userlevel 2
+5
I know we can technically choose what suits us, but tbh names are more of an inclusion issue than most people realize (usually people who go by the same name as what’s on their drivers license). Having processes in place to verify the name that employees prefer will go a long way towards making them feel “at home” in your organization. (I am one of these people and can confirm that being called Rebecca at previous jobs was really jarring, always. And I consider that to be mild compared to other slights you could potentially inflict on employees by not using a preferred name.)
As for the double last name, I suggest opting for a streamlined neutral option like first.lastlast, and allowing the employee to choose one of the names if they want. Messing around with two last names can already have issues with username field limits (particularly in Slack), no need to add hyphens and stuff in there too.
Open Thread in Slack
Userlevel 3
+3
Agreed on the preferred name and how it's actually a key part of being an inclusive organization. Which is why its so surprising to me that ADP make it so hard for preferred first and last name to be input in a systemic way
Open Thread in Slack
We use ADP as well and it will be the death of me. Because of this we've moved to having first and last name only created from ADP, but controlled via Okta. Then we store the original legal name in separate fields in Okta for use with any systems that need to use a legal name.
There are probably better ways to handle it, but no one has time to revisit it, ha.
Open Thread in Slack
Userlevel 3
+3
My internal adp person told adp that because they don't make preferred names easy to get access to, we might have to leave them
Open Thread in Slack
Reply
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.