Record the Source of Truth for Employee Email Identity Changes

Separate the fields before deciding

“Employee identity” can mean several different things: a person’s preferred display name, the name shown in a directory, or the mailbox address used to send and receive email. A request may concern only one of these, even if it casually asks to “change the email.” Treat each field as a separate decision. A display-name update does not necessarily require a new address, and an address change should not be assumed to change every directory or account record.

Write down exactly what is being requested. For example: “Update the display name from [current name] to [approved name]” is clearer than “fix the account.” This makes it easier to compare the request with the source or approval that is supposed to govern that particular field.

Choose the authority before a conflict arrives

The organization should identify, in its own procedures, which record governs each change and who can approve exceptions. That might mean an authorized employee record governs a legal or organizational name, while a designated business approver confirms a mailbox-address change. The right authority depends on the organization’s policies; do not assume that the person who sent the message, manages the employee, or administers mail automatically has authority over every field.

Make the rule specific enough to use. Record the name of the source system or document, the role authorized to approve a change, and what to do if they disagree. If there is no approved rule, ask the responsible organizational owner to establish one before processing a disputed change.

Pause when the evidence does not agree

If a manager requests one address but the authorized record shows another, do not choose whichever request seems more recent or convenient. Hold the change, note the conflicting values, and contact the designated approver through an established channel. Ask a focused question: which value should be used, which record or approval supports it, and does the decision apply to the address, the display name, or both?

Share only the information needed to resolve the discrepancy. Avoid forwarding unrelated personal details or asking people to send passwords or one-time codes. If the authorized approver cannot be identified, escalate to the process owner rather than treating silence as approval.

Keep a decision record that another admin can follow

Document the request date, the field being changed, the requested and approved values, the governing source or approver, and the reason for any exception. Note who resolved a discrepancy and when. Keep the record in the organization’s approved location, with access limited according to its internal practices. The purpose is to make the decision understandable later, not to collect unnecessary employee information.

Keep the decision record separate from the change itself. A saved note or approval does not prove that the mailbox or profile was updated. Record the implementation separately, including who made it and when, using whatever administrative recordkeeping process your organization authorizes.

A worked example

Suppose a manager asks to change an employee’s address to [riley.chen]@example.com, while the organization’s designated employee record lists [riley.chan]@example.com. The admin pauses rather than editing the mailbox. The admin checks which record governs address changes, then asks the authorized approver to resolve the mismatch. The approver confirms the correct address and explains that the manager’s request used an outdated spelling.

The admin records the conflicting values, the governing source, the approver’s decision, and the date. After the authorized change is made, the admin confirms the resulting address and display name against the approved values, then tells the employee and relevant requestor what changed. This confirms the intended outcome without treating the original request as authority.

Use a short confirmation checklist

Before closing a request, verify the decision and the result rather than relying on the absence of an error message. Follow the organization’s access and change-control procedures, especially if more than one administrator can update accounts.

• Is the requested field clearly identified?
• Is the governing record or authorized approver recorded?
• If sources conflicted, is the resolution and its owner documented?
• Does the resulting address or name match the approved value?
• Have the employee and relevant requestor received an appropriate confirmation?