When one person works across several brands, an email address alone is a poor guide to who they are or which organization they represent. A familiar pattern may suggest an affiliation, but names, domains and responsibilities can change—and an address can be shared, redirected or used for a different purpose. A simple identity map gives colleagues a dependable place to check the relationship between a person, their organizations and the addresses they use. It is a reference record, not proof of identity or a replacement for your mail system’s account and access controls.
The useful bits
- Record people, affiliations and addresses as separate, connected facts.
- Label each address by purpose and whether it is a mailbox or alias.
- Assign an owner and a routine for checking changes.
Start with the person, not the address
Make one record for each individual, using a stable internal identifier if your organization already has one. Keep the person’s preferred display name separate from the address: display names can be edited, and two people may have similar names. Avoid treating a domain or a matching name as sufficient evidence of someone’s organizational role.
Then list each current affiliation explicitly. That could be an employer, subsidiary, brand team or project organization. If the person’s relationship is temporary or limited to a particular responsibility, record that context and, where useful, when it began or is expected to end. Do not infer authority from affiliation; the map explains relationships, while your approval and access processes determine what a person may do.
Give every address a purpose
Record each address exactly as it is used, including its domain, and connect it to the person and relevant affiliation. Add a plain-language purpose such as customer support, supplier correspondence or internal coordination. If the address is shared, say so and identify the responsible team or owner rather than attributing every message to one individual.
Also identify the address type. An alias can route mail without being an independent mailbox or login. A shared address, alias and individual mailbox are not interchangeable, so note which applies only after checking the organization’s actual configuration. Record whether the address is active, retired or awaiting confirmation; do not leave old addresses looking current.
Choose fields colleagues can maintain
Keep the record small enough to update. A useful entry includes the person’s name or identifier, affiliation, address, address purpose and type, status, and a contact or team responsible for confirming the entry. Add a last-confirmed date if it helps your team notice stale records. Use your approved internal directory or other controlled location, and limit access to people who need the information.
Do not put passwords, one-time codes, recovery details or unnecessary personal information in the map. It should point colleagues toward the right organizational context, not become a credentials store or a second, unmanaged account system. If a detail is uncertain, mark it for confirmation instead of filling the gap with a guess.
A practical cross-brand example
A colleague looking up either address can now see the person’s stated relationship and the intended context without guessing from the domain. If the second address is only an alias, the record says so; it does not imply a separate login or independent inbox.
Person: [employee name or internal ID] Affiliation: [outdoor brand] Address: [employee]@[outdoor-brand].example.com Purpose: [outdoor brand] customer correspondence Type/status: [individual mailbox] / [active] Affiliation: [home-goods brand] Address: [employee]@[home-brand].example.com Purpose: [home-goods brand] supplier correspondence Type/status: [alias or mailbox—verify] / [active] Record owner: [team or role] Last confirmed: [date]
Make changes visible and verifiable
Set a simple change process: when someone joins, changes responsibilities or leaves an affiliation, the responsible team updates the person, affiliation and address entries together. When an address is retired, mark it inactive and record the replacement only after the relevant owner confirms it. Periodic review by the record owner can catch stale entries, but a review date is not proof that the underlying mail configuration remains correct.
To confirm an update worked, ask the responsible mailbox or workspace administrator to verify the address type, status and organizational association in the systems they are authorized to manage. Then have a colleague who did not make the change look up the address and explain who it belongs to, which affiliation applies and what the address is for. If they cannot do that from the record, clarify the entry or its ownership. Keep the map and actual account permissions distinct: an accurate reference does not itself create, remove or authorize an account.
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
