An employee changes their name, but their email address may appear in far more places than their inbox: directories, meeting invitations, shared documents, contact lists, and sign-in records. Changing everything at once can interrupt work; changing nothing can leave a name the employee no longer uses in routine communications. A clear policy helps administrators make a consistent choice with the employee, keep necessary correspondence reachable, and verify each update. The goal is not to assume every system works the same way, but to follow a documented sequence and confirm the outcome.
The useful bits
- Ask the employee which name and address they want used, and distinguish a display-name update from an address change.
- Plan continuity before changing an address; confirm which options the mail service actually supports.
- Check mail, directory entries, calendars, sign-in records, and external services after the change.
Start with a consistent decision rule
Write down how your organization handles name changes before a request arrives. The policy should say who receives the request, who can approve or make changes, how the employee’s preference is recorded, and which records are in scope. Keep access limited to people who need to carry out the work, and avoid asking for personal details unrelated to the change.
Separate two decisions: what name appears to recipients, and whether the actual email address changes. An employee may want a new display name while keeping an established address, or may request both changes. Ask rather than infer. Apply the same criteria across employees, while allowing a documented exception when a business or technical constraint requires one.
Choose whether the address itself should change
Consider the employee’s preference, how the address is used, and the work required to update it. If the address is embedded in customer contacts, account sign-ins, distribution lists, or records, changing it may require coordination beyond the mail system. If the employee requests a new address, agree on a target format that fits your organization’s naming convention and check availability through an authorized administrator.
A display-name change is not the same as changing a mailbox address or login. Do not assume that an alias, forwarding arrangement, or secondary address is available, or that it creates a separate mailbox or sign-in. Before promising continuity, have an authorized administrator confirm what the current service and account provisioning support. If the address cannot be changed, explain the constraint and agree on the best supported alternative.
Employee request: “Please use Jordan Lee in messages. I would also like my address reviewed.” Decision: Update the displayed name first. Check the requested address and dependent sign-ins before agreeing to change the mailbox address. Illustrative address format only: jordan.lee@example.com
Plan continuity before making the change
List the places where the current address is used: incoming mail, internal directories, team lists, calendar invitations, shared files, contact cards, and external services where the address is a username or recovery contact. Identify who owns each system. Do not assume that changing a mailbox setting updates those records automatically.
Agree on how long, if at all, the former address must remain usable for incoming correspondence. The appropriate arrangement depends on available controls, business needs, and your organization’s retention and access rules. Confirm the actual behavior before communicating it. Avoid silently redirecting mail to another person; access to an employee’s correspondence should follow established organizational controls.
Update records in a controlled sequence
Coordinate the timing with the employee and the administrators responsible for mail and other identity systems. Update the mail profile or address only through controls available to an appropriately authorized administrator or account holder; available actions can depend on role, plan, and provisioning. Where BITTU Mail is used, workspace administration is subject to those conditions, so confirm the available controls rather than relying on an assumed menu or workflow.
Then review the organization’s directory and connected records. Check the visible name, address, sign-in identifier, calendar ownership or invitations, group memberships, and contact details wherever they are maintained. Update the employee’s signature if appropriate, and ask them to review any personal profile information they control. For third-party services, use each service’s approved account-update process.
Use a short, employee-approved notice
Agree on who needs to be told and what the notice should say. For internal colleagues, a brief update can identify the name and address to use without explaining the reason for the change. For external contacts, send a notice only where it is useful and appropriate. Do not imply that every recipient’s address book or mail system will update itself.
Keep the employee involved in reviewing the wording, recipient list, and timing. If a transition period is supported, describe its limits accurately. A notice is not proof that every message will reach the right place, so provide a suitable contact route for questions during the change.
Confirm the change and close the loop
After updates are made, ask the employee to check the name and address shown in a new message and in their account profile. Have an authorized colleague verify the relevant directory entry and, where appropriate, send a routine test message to the agreed address. Confirm that replies display the intended name and that calendar invitations or other key workflows use the correct identity.
Check the sign-in identifier separately from the public-facing address, since they may not be the same. Confirm changes with the owners of important external accounts rather than assuming their records followed the mail update. Record what was changed, what remains pending, who owns each follow-up, and any approved continuity arrangement. Close the request only after the employee knows what changed and how to report a missed update.
- Before: confirm the employee’s preferred name, whether the mailbox address should change, and who is authorized to act.
- During: check availability and supported continuity options; update mail and dependent identity records with their owners.
- After: verify profile, directory, sign-in, and key communication workflows; tell the employee what remains outstanding.
About this guide
Prepared with AI assistance for the BITTU Mail editorial library. Check important details against your original messages and current account settings. Product access depends on your role, plan and provisioning state. Provider interfaces and requirements can change.
View current plans · Security information · Suggest a correction

