Create a consistent email naming policy so new staff, departments and name changes can be managed predictably. The policy should define ownership and lifecycle as well as how an address looks.
IN THIS ARTICLE
01 Write and apply the policy
- Select a readable format for named users and define how to handle duplicate names, punctuation, name changes and transliteration where relevant.
- Separate personal identities from role addresses such as accounts or support. Decide whether each role address is an alias, group or shared mailbox.
- Reserve important operational names and record who owns them. Review any product restrictions before promising that a particular address can be created.
- Define how old addresses are retained after a rename and who can approve forwarding or reassignment. Avoid giving a new employee access to a former employee's identity by accident.
- Record the creation, change and retirement process. Include checks for groups, signatures, directory entries, application logins and recovery contacts.
- Apply the policy to a small set of test cases, including two people with the same name and a department changing responsibility.
- Publish the approved internal guidance and review it when the organisation changes its domain or email product.
02 Example: test a naming policy before creating accounts
Assume the approved format is [email protected]. The first Alex Musa receives [email protected]. If another Alex Musa joins, the policy might assign [email protected] after checking the directory. Record the chosen collision rule so administrators do not improvise a different pattern each time.
The department address [email protected] should have a separate owner and delivery model. If it is currently an alias for the finance manager, a staff change requires an explicit review of its destination and reply identity. A personal name change also needs checks for the old address, groups and external logins. These are illustrative conventions, so apply your organisation's approved policy and the provider's supported address rules.
Common questions
Can an alias replace a new employee's account?
An alias adds an address to an existing destination; it does not create a separate identity. Give each person the appropriate individual account.
Should a departed employee's address be reused immediately?
Consider confidentiality, old correspondence and account-recovery links first. Use a deliberate retention and reassignment policy.
Must the display name match the email spelling exactly?
The display name can be more readable, but it should identify the sender honestly. Test how it appears externally and keep directory information consistent.