Discussion Locked

Identity Management and Legal Names

0 helpful
1 reply
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have put in an Identity Management solution with our HR Database as the authoritative Source for employee names. The system automatically provisions User IDs based on first initial of first name+last name to 8 characters. This same ID becomes their e-mail address. A User Portal sits on top of this to display an internal Phone Directory for all Employees.

We continually fight battles however over employees who don't want to use their legal last names, don't like their shortened user IDs or e-mail addresses, etc. It's the holy war of naming and they take it all the way up the chain to get exceptions made.

I'm sure others are running into this as they attempt to standardize and automate Identities across the organization. I'd like to hear how you're company is handling this?

1 reply

by bob

Consistency is key. You need to get buy-in from upper management that no exceptions can be made. You can play it off like it's a security issue (meaning no unknown addresses are used), a customer service issue (easy to remember names), etc.

However, typically you'll see logins like first initial plus last name, and the email will be firstname dot (.) lastname @ domain.com But I can see some users frowning at that too

That's where you can keep a "nickname" field and if it's populated, go ahead and use that as the first name, like "john.smith@u.com" versus "johnathan.smith@u.com"

For those users who dislike having their legal names shown, tell them it is more professional. Having "sueb" for Susan Barockovich isn't professional looking, and it even makes it seem like your company is very small to be able to do that, and have an undefined email naming policy.

Good luck

-idbob

http://www.identityforums.com

This discussion is closed to new replies.