> For the complete documentation index, see [llms.txt](https://docs.harmony.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.harmony.io/people-management/configuring-domain-aliases-for-employee-identity-matching.md).

# Configuring Domain Aliases for Employee Identity Matching

When your organization uses different email domains across integrations - for example, a legacy domain in your MDM while employees log in with a newer domain in Okta - Harmony may create duplicate user records instead of recognizing these as the same person. Domain alias support lets you tell Harmony which domains are equivalent, so employee identities are unified correctly across all connected integrations.

This is especially useful during domain migrations, acquisitions, or any situation where a single employee might appear under more than one email domain depending on the source system.

### How Domain Aliases Work

When you configure a domain alias, Harmony treats the alias domain as equivalent to your primary domain when matching employee records. For example, if your primary domain is `company.com` and you add `oldcompany.com` as an alias, an employee appearing as `jane@oldcompany.com` in your MDM will be matched to `jane@company.com` in Okta and unified into a single identity.

This means:

* Asset assignments from integrations using the alias domain are correctly attributed to the right employee
* Ticket routing works as expected regardless of which domain appears in the source system
* Duplicate user records caused by domain mismatches are eliminated automatically

Harmony resolves identities using either domain without any manual merging required.

### Configuring Domain Aliases

To add a domain alias for your employee directory:

1. Navigate to **Settings** in the Harmony sidebar.
2. Select **People Management** from the settings menu.
3. Locate the **Employee Directory** section and open the **Domain Aliases** configuration.
4. Click **Add Alias**.
5. Enter the alias domain you want to map - for example, `oldcompany.com`.
6. Confirm the primary domain it should resolve to.
7. Save your changes.

You can add one or more aliases to cover all alternate domains your organization uses.

### When to Use Domain Aliases

Consider configuring domain aliases in the following situations:

* **Domain migration** - Your organization is moving from one email domain to another, and different integrations are still using the old domain during the transition period.
* **Acquisitions or mergers** - Employees from an acquired company retain their original email domain in some systems while being onboarded to the parent company domain in others.
* **Multiple email domains** - Your organization operates under several domains and different tools authenticate users under different ones.
* **Okta and Google Workspace mismatches** - Your Okta login domain differs from the domain used in Google Workspace, your MDM, or other connected tools.

### What to Expect After Saving

Once you save a domain alias, Harmony begins applying it to identity resolution across all connected integrations. Existing duplicate records caused by the domain mismatch will be unified, and going forward, Harmony will automatically resolve employees regardless of which domain appears in the source data.

No additional configuration is required within individual integrations. The alias applies globally across your employee directory.

### Considerations

* Domain aliases are applied at the directory level and affect all integrations simultaneously.
* Adding an alias does not modify data in the connected source systems - it only affects how Harmony matches and displays employee identities internally.
* If you need to remove an alias, return to the **Domain Aliases** configuration, locate the entry, and delete it. Harmony will stop resolving that domain as equivalent to the primary domain on the next sync.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.harmony.io/people-management/configuring-domain-aliases-for-employee-identity-matching.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.