> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/guides/data-management/change-primary-email.md).
# Change a user's primary email
Fix a mismatched primary email so integration actions resolve against the right address, without asking support.
### What this guide helps you achieve
Siit syncs email addresses from your HRIS and identity provider. Sometimes it ends up holding the wrong one as primary, for example after an email change in the HRIS, or when your IdP has both an active and a suspended profile for the same person. When that happens, integration actions (adding someone to a JumpCloud group, an Okta action, and so on) can fail silently because they're targeting the wrong address.
This guide shows you how to correct it yourself from the People overlay.
#### Before you start
* You need a role with user-management permission (same access level required to merge users).
* The person needs more than one known email address. If they only have one, there's nothing to change and the option won't appear.
#### Steps
1. Go to **Context → People** and open the person's profile.
2. Click the ***`...`*** actions menu (next to Merge user) and select **Change primary email**.
3. In the **Email addresses** list, pick the address that should become primary. The current primary is pre-selected.
4. Click **Save**.
You'll see a confirmation once the change goes through, and the profile refreshes to show the new primary email.
#### Frequently asked questions
**What happens to the old primary email?**\
It stays attached to the person as a known address; it's just no longer the one integrations use.
**Will this affect the person's login or verified accounts?**\
No. This only changes which address Siit treats as primary for provisioning and lookups. It doesn't touch account verification.
**Where can I see that a change was made?**\
Every change is logged as a timeline event on the person's profile, showing the new address and the one it replaced.
**Is this available on my plan?**\
Yes, this is available on all plans.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.siit.io/guides/data-management/change-primary-email.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
