> 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/using-peakcommerce/users-and-user-roles/editing-a-user.md). # Editing a User People change teams, change responsibilities, and occasionally need their access reset. Editing a user lets you adjust what they can do without recreating their account — their history, audit trail, and identity stay intact. ## Open a user Open the **user menu** (your name, bottom-left) → **Settings → Users**, then click a row to open the user's detail page, or use the row menu (**⋯ → Edit**). The detail page has tabs for **Activity**, **Logins**, **Impersonations**, and **Details**; the header carries the quick actions and the **Actions** menu described below. ## What you can change * **Role and Profile** — choose **Edit** to change what the user can access. As with creating a user, the Profile list filters to the selected role. See [User Roles](/product/using-peakcommerce/users-and-user-roles/user-roles.md) and [User Profile Overview](/product/using-peakcommerce/profiles-and-permissions/user-profile-overview.md). * **Email** — because sign-in is via Auth0, updating the email updates their login; use **Actions → Change Email** (below) so the change syncs to the identity provider and the user re-verifies the new address. * **External Account** — for customers and partners, update the linked External Account ID to point the user at the right billing account. * **Deactivate / Reactivate** — revoke or restore access without deleting the record (see [Suspending Users](/product/using-peakcommerce/users-and-user-roles/suspending-users.md)). You can't deactivate yourself. * **Impersonate** ("Log in as") — for support staff with permission, sign in as the user to reproduce what they see. This is recorded in the audit trail. ## Header quick actions The detail-page header carries one-click actions (each destructive one confirms first): * **Impersonate** — shown when you hold the impersonate permission and the target isn't you or a system administrator. * **Reset password** — on Auth0-backed tenants, emails the user a secure link to set a new password. You never see or type the password — Auth0 manages it — and this is the **only** way to change a credential; there is no admin "set password" field anywhere in PeakCommerce. * **Edit** — opens the edit form for role, profile, and details. * **Deactivate / Reactivate** — as above. ## The Actions menu On Auth0-backed tenants, the header also carries an **Actions** menu with identity-level operations: * **Send Verification Email** — re-sends the address-verification email for the user's current address. * **Change Email** — updates the address in Auth0 (marking it unverified and sending a fresh verification email), then syncs it to PeakCommerce. The user keeps the same account and history. * **Change Phone Number** — stored on the Auth0 identity and mirrored here. It's contact metadata, not a sign-in factor. * **Block / Unblock** — stops the user signing in at the identity provider without touching their PeakCommerce record. If the sync to Auth0 fails you'll see a warning — the block isn't effective until it succeeds, so retry. * **Reset MFA Enrollment** — after a confirmation dialog, removes all of the user's enrolled multi-factor authenticators; they'll be prompted to enroll a new factor at next sign-in. Use this for a lost or replaced device. * **Delete** — permanently removes the user from PeakCommerce **and** deletes their Auth0 identity. You must type the user's email address to confirm, and the option never appears on your own account. Delete is also still available from the list row's **⋯** menu on the Users page — the detail page's type-to-confirm flow is the safer route. Prefer **Deactivate** when you may need the record later. ## Gotchas * Changing a role narrows or widens access immediately — re-check the assigned Profile after switching roles, since a profile built for one role won't fit another. * **Block** and **Deactivate** are different levers: Deactivate is PeakCommerce-side and reversible in place; Block acts at the identity provider and is what stops an SSO sign-in. * Users can edit a limited set of their own details (display name, login email, password) from **My Profile** in their own portal. --- # 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/using-peakcommerce/users-and-user-roles/editing-a-user.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.