At my company, when an employee changes their name, we update their account details and email address, but only keep the previous email as an alias for 30 days. After that, the alias is removed because the company is worried that a future hire might have the same name. In practice, this causes bounced messages, missed communication, and confusion for people who still have the old address saved. How does your organization handle name changes and potential duplicate names?
5 Answers
The old address should generally remain as a receive-only alias indefinitely. People may continue using it for years, and there is little benefit to deleting it. If a new employee has the same name, handle that as a normal naming conflict by adding a middle initial, number, or another unique identifier.
The cleanest setup is to make the permanent username an employee ID or another non-name-based identifier, then use email addresses only as aliases. That way a name change does not affect the underlying account, audit history, or integrations, and duplicate names are no longer a reason to delete anything.
Never reuse an old email address or username. A new owner could receive sensitive messages or potentially reset accounts that were still tied to that address. Keep the address associated with the original account, even after the employee leaves, and use a unique identifier for new accounts.
Thirty days is far too short. If the company insists on eventually retiring aliases, a much longer period such as a year would be safer, but permanent retention is preferable. Old contacts and customers often do not learn about a name change immediately, so removing the alias guarantees avoidable bounced mail.
We keep previous addresses as aliases for as long as the employee has the account, and sometimes beyond that. Name changes, marriages, divorces, and even people changing their names back are much easier when the old address still routes correctly. A shared departmental address can also help avoid tying important business communication to a person's name.
Exactly. Deleting an existing alias to solve a hypothetical future collision creates an immediate, real problem. The same naming-conflict process should apply whether the address belonged to a former employee or someone who currently works there.