Understand session regeneration improvements | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/understand-session-regeneration-improvements Publisher: Pixie Technologies LLC Core CRM security hardening Understand session regeneration improvements Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. This guide explains improved session-identifier replacement around authentication and security-sensitive state changes. Audience: Administrators and deployment engineers; Permission: Core release / deployment authority; Where to goAutomatic core protection — no separate staff menu route What this guide helps you do Understand improved session-identifier replacement around authentication and security-sensitive state changes. The workflow below follows the supported application or module flow and does not invent a menu or bypass validation. Follow these steps - Use the supported Pixie CRM release or workflow that produces this security control. - Check the expected protection through an authorised test. - Record the result in the deployment or security audit evidence. Fields and options - Authenticated session identifier Rules and limits - Session identifiers are regenerated while legitimate session data remains available. - Prior identifiers must not remain reusable after the protected transition. - Users must not copy session cookies between accounts or browsers. Check it worked - The protection is active without weakening another security control. Security, audit and troubleshooting checks - Use the exact authorised account, role and record before saving or sending. - Verify the saved status and downstream record; a browser success message alone is not sufficient evidence. - Never expose passwords, API keys, access tokens, protected attachments or raw server paths in support tickets. - Do not edit module or core database records directly to bypass validation, permissions, migrations or state rules. Related guides Use secure HttpOnly and SameSite cookie defaults (https://pixiecrm.com/help-centre/use-secure-httponly-and-samesite-cookie-defaults)Verify the corrected two-factor assignment flow (https://pixiecrm.com/help-centre/verify-the-corrected-two-factor-assignment-flow)Apply two-factor authentication throttling (https://pixiecrm.com/help-centre/apply-two-factor-authentication-throttling)Understand restricted CSRF exclusions (https://pixiecrm.com/help-centre/understand-restricted-csrf-exclusions)