Troubleshoot a core security hardening deployment | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/troubleshoot-a-core-security-hardening-deployment Publisher: Pixie Technologies LLC Core CRM security hardening Troubleshoot a core security hardening deployment Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Diagnose security-release failures without disabling the new controls. Audience: Administrators and deployment engineers; Permission: Core release / deployment authority; Where to goSupported Pixie CRM deployment and database-upgrade process — no staff menu route What this guide helps you do Diagnose security-release failures without disabling the new controls. 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 - Exact timestamp and route - Expected/actual version - Migration state - Security/audit evidence Rules and limits - Verify the deployed code, migrations and seed versions match. - Check application, web-server and central security logs. - Correct proxy trust, certificate chains, cookie domain or integration configuration as applicable. - Do not resolve faults by disabling TLS, throttling, CSRF, secure cookies, auditing or upload protections. 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 Run the post-upgrade security verification checklist (https://pixiecrm.com/help-centre/run-the-post-upgrade-security-verification-checklist)Confirm removal of unnecessary runtime development artefacts (https://pixiecrm.com/help-centre/confirm-removal-of-unnecessary-runtime-development-artefacts)Verify the updated future-tenant database seed (https://pixiecrm.com/help-centre/verify-the-updated-future-tenant-database-seed)Apply Pixie CRM SaaS migration 040 (https://pixiecrm.com/help-centre/apply-britixo-saas-migration-040)