> For the complete documentation index, see [llms.txt](https://docs.openiam.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openiam.com/end-user-guide-for-selfservice/your-profile/edit-profile.md). # Editing your profile Change your personal details, confirm a new email or phone, and understand approvals. Open **Edit Profile** from your account menu → **Profile → Edit Profile**. ## Making a change {% stepper %} {% step %} **Open Edit Profile and change what you need.** Fields you are not permitted to change are shown but locked. Required fields are marked — the page tells you which are missing when you try to save, for example *"Field 'Middle Name' is required"*. {% endstep %} {% step %} **Save.** If nothing further is needed, you see *"User Profile was saved successfully"* and the change is live. {% endstep %} {% step %} **Confirm a new email or phone number, if you are asked to.** See [Confirming a new email or phone](#confirming-a-new-email-or-phone) below. {% endstep %} {% step %} **Wait for approval, if your organization requires it.** See [When a change needs approval](#when-a-change-needs-approval) below. {% endstep %} {% endstepper %} ## Confirming a new email or phone Because contact details are used to verify who you are, changing them is treated carefully. If your organization has switched this on, saving a new email address or phone number does not apply it immediately. Instead: 1. A **confirmation code** is sent to the **new** address or number — not the old one. This proves you can actually receive messages there. 2. You are taken to a confirmation page and type the code in. 3. If you changed both email and phone, you get a separate code for each, and both must be confirmed. 4. Only once confirmed does the new detail replace the old one. {% hint style="warning" %} The confirmation code expires after **15 minutes**. If you take longer, the code stops working and a new one is issued when you try again — so open the message promptly. {% endhint %} If a code never arrives, the address or number you typed is probably wrong. Go back and check it character by character — the code went to the new value, so a typo means it went nowhere useful. ## When a change needs approval Some organizations route profile changes through an approval step, so that a person checks the change before it reaches your other accounts. When that applies: * Saving creates a **request** rather than an immediate change. * Your existing details stay in place until the request is approved. * You can follow it in [Request history](/end-user-guide-for-selfservice/requests/request-history.md). * You are notified when it is approved or rejected. Whether this happens, and which fields trigger it, is your organization's choice — so a change that applies instantly for a colleague at another company may need approval at yours. ## Messages you might see | Message | What it means | | ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------- | | *"User Profile was saved successfully"* | Done — the change is live. | | *"User Profile could not be saved"* | Something prevented the save. Check for fields marked in error and try again; if it persists, contact your help desk. | | *"Field '…' is required"* | A mandatory field is empty. | | *"Value '…' is not valid for element '…'"* | The value doesn't match the expected format for that field. | | *"Can't have a blank email"* | An email address is mandatory and cannot be cleared. | | *"Email '…' is not valid"* | The address is malformed — check for a missing `@`, a stray space, or a typo in the domain. | ## What happens after your change A saved change does not stay inside OpenIAM. Depending on how your organization is set up, it can flow out to your connected accounts — the network directory, email system, and business applications. That is the point: correct it once, and it is correct everywhere. Propagation is not always instant. If a colleague still sees your old details in another system an hour later, that is usually normal timing rather than a failure. --- # 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.openiam.com/end-user-guide-for-selfservice/your-profile/edit-profile.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.