> 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/authentication-and-security/session-management.md). # Session Management A **session** represents an authenticated user's connection to PeakCommerce. While a session is active, the user moves through the app without signing in again. Sessions matter for security because a session that never ends is a standing invitation to anyone who gets hold of a device — so PeakCommerce ties every session to a defined lifetime and ends it the moment credentials change. ## How sessions work PeakCommerce delegates authentication to **Auth0**. When a user signs in, Auth0 establishes a login session on its authorization server, and the application keeps its own server-side session so it can tell, on each request, whether the user is authenticated. That local session is backed by the database (not just a cookie), and the session cookie is sent over HTTPS, marked HTTP-only, and scoped so it can't be read by page scripts. Signing in with a social or enterprise identity provider (for example Google or an OIDC IdP) adds that provider's session as well — which is what enables a seamless **single sign-on** experience: a user already signed in to Auth0 (or to a linked provider) can be signed into PeakCommerce without re-entering credentials. ## Session lifetime Sessions have an **absolute lifetime** of 24 hours. Once that limit is reached, the user must sign in again regardless of recent activity. There is no separate idle-timeout window today — the clock is fixed from sign-in, not from last action. ## When a session ends * **The user signs out.** Logout destroys the local session and, for SSO users, also clears the Auth0 session (federated logout) so the next sign-in re-authenticates rather than silently resuming. * **The 24-hour lifetime is reached.** * **The user's password or email is reset**, or the account is deactivated. When a user is signed in across paired branded hosts, signing out of one coordinates logout across the linked hosts in the same session group. ## Related * [Single Sign-On for PeakCommerce Sites](/product/using-peakcommerce/authentication-and-security/single-sign-on-for-peakcommerce-sites.md) * [Password Policies](/product/using-peakcommerce/authentication-and-security/understanding-and-configuring-password-policies-in-peakcommerce.md) --- # 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/authentication-and-security/session-management.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.