> 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/suspending-users.md). # Suspending Users Suspending a user revokes their access without deleting the record — the right move when an employee leaves, a contract ends, or you need to pause someone temporarily. Their role, profile, and history are preserved, so reactivating later restores them exactly as they were. In PeakCommerce this is done with the **Deactivate** / **Reactivate** controls. ## Why deactivate instead of delete Deactivating keeps the user in your records for auditing and lets you restore access in one click. Deleting is permanent and removes the account from PeakCommerce and Auth0. When in doubt, deactivate. ## Deactivate a user 1. Open the **user menu** (your name, bottom-left) → **Settings → Users**, then open the user. 2. In the header, choose **Deactivate** and confirm. Their **Status** changes to inactive and they can no longer sign in. They still appear in the [users list](/product/using-peakcommerce/users-and-user-roles/viewing-your-users-list.md) for record-keeping, and the change is written to the audit trail (see [User History](/product/using-peakcommerce/users-and-user-roles/user-history.md)). ## Reactivate a user Open the inactive user and choose **Reactivate**. Their status returns to **Active** and access is restored with the same role and profile they had before. ## How it works Deactivation flips the user's active state in PeakCommerce; on the next sign-in attempt the platform refuses the session. For **Customer** users, deactivation in the connected billing system can also remove the customer's portal access, since the user is tied to an External Account — so a billing-side change may take effect even if you didn't touch the user here. See [Authentication & Security](/product/using-peakcommerce/authentication-and-security.md). ## Gotchas * An active impersonation session is not a way to bypass deactivation — once a user is inactive, new sign-ins (theirs or an impersonator's) are blocked. --- # 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/suspending-users.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.