> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/settings/access-security/my-profile.md). # My Profile **Settings → My Profile** is where you manage your own account — the personal details that identify you across PeakCommerce and the preferences that shape how the app behaves for *you* specifically, independent of organization-wide configuration. ## Why it matters Your profile is the record other people see when you create journeys, edit components, or appear in audit and activity logs. Keeping your name and login email correct keeps that attribution clear, and setting your own display timezone means dates and times across the product read in *your* local time rather than the organization's default. ## What you can edit * **Name** — how you're shown throughout the app and in activity/audit trails. * **Login email** — the address you sign in with and where account notifications go. * **Display timezone** — a personal override of the organization default. Only the way times are *displayed* to you changes; it does not alter how data is stored or how times appear for teammates. ## Password & sign-in Passwords and the sign-in flow are handled by Auth0, not in this page — there's no "change password" field here. To reset a password or set up multi-factor authentication, use the sign-in screen's recovery options. If you can't get in, see [Trouble Signing In](/product/settings/settings-overview/unable-to-login-to-peakcommerce.md). ## Gotchas * Changing your **login email** changes the credential you authenticate with — use an address you control. * A personal **timezone** override only affects you; to move the whole organization's default, an admin updates Company Settings instead. --- # 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.peakcommerce.com/product/settings/access-security/my-profile.md?ask=&goal= ``` `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.