At my company, when someone changes their name, we update their login and email address but keep the previous address as an alias for only 30 days. After that, the alias is removed, supposedly to avoid conflicts if a future employee has the same name. In practice, this causes bounced messages and missed communications. How do you handle employee name changes, duplicate names, and old email addresses?
4 Answers
A good setup is to use a permanent employee ID or other neutral internal username, while treating the name-based email address as an alias. When someone changes their name, add the new address as the primary one and retain the previous address as receive-only. Some organizations keep former employees’ addresses unavailable permanently or for a very long retention period.
The old address should normally remain as an alias indefinitely, or at least for as long as the person has an account. People and external contacts may continue using the old address for years, and an alias costs very little. If another employee has the same name, handle that with your normal collision policy—add a number, middle initial, or another unique element—instead of deleting an existing address.
Exactly. You already have a real problem—lost mail—in order to prevent a hypothetical naming conflict. The same naming policy should apply whether the conflict comes from a new hire or an old alias.
If your organization insists on removing aliases, 30 days is far too short. A longer transition period—six or twelve months—could encourage people to update their records, but it still won’t catch every customer, vendor, or automated system. Permanent aliases are generally the safer operational choice.
Never reuse an old email address or username for a different person. A new employee receiving messages intended for a former employee can expose sensitive information, and old addresses may still be tied to external accounts. Keep the old address attached to the original identity and make the new person’s address unique.
This is especially important when the address was used for business services or password recovery. Reusing it can create both privacy and security issues.
This also makes future name changes painless. People may change their surname more than once, and keeping the aliases means mail delivery continues without repeated migrations.