Understand Letter Manager client data isolation | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/understand-letter-manager-client-data-isolation Publisher: Pixie Technologies LLC Customer profile and client portal Understand Letter Manager client data isolation Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Confirm client history and view routes restrict records by the logged-in customer ID. Audience: Administrators, clients and security teams; Permission: Authenticated staff account; Module v1.0.0; Where to goClient Area → Letter History / View Before you start - Use an authorised account and confirm the customer, external recipient, template, letter or configuration is the intended one. - Follow the exact route shown above and verify the stored record, generated file and delivery evidence instead of relying on an alert alone. What this guide helps you do Confirm client history and view routes restrict records by the logged-in customer ID. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow. Follow these steps - Test with two controlled customer accounts. - Verify each account sees only records with its own client_id. - Attempting a different numeric view ID should return 404. - Report any exception immediately. Fields and options Action scopeVerify client history and view routes restrict records by the logged-in customer ID. Module version1.0.0 Exact routeClient Area → Letter History / View EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow. Rules and limits - Both client controllers derive client_id from the session. - The single-letter view applies id and client_id in the database query. - External records are not shown because they have client_id=0. Check it worked - The requested letter, template, setting, file or tracking detail is created or updated through the supported route. - The history row, generated PDF, email/send metadata, public verification, signature evidence, client view or postal display agrees with the action. - Any warning, missing file or failed send is investigated rather than bypassed. Security, privacy and operational checks - Apply least privilege and verify recipient identity before sending or exposing public links. - Protect PDFs, enclosures, signatures, verification URLs, email-open metadata, IP addresses and customer data under organisational policy. - Test configuration and deployment changes with controlled records before production-wide use. - Interpret email opens and e-signatures according to their documented technical limitations. Related guides Letter Manager module overview (https://pixiecrm.com/help-centre/letter-manager-module-overview)Use the standalone Letter Manager portal history (https://pixiecrm.com/help-centre/use-the-standalone-letter-manager-portal-history)Search standalone client Letter History (https://pixiecrm.com/help-centre/search-standalone-client-letter-history)Configure SMTP email delivery (https://pixiecrm.com/help-centre/configure-smtp-email-delivery)Add and manage customer contacts (https://pixiecrm.com/help-centre/add-and-manage-customer-contacts)Client portal overview (https://pixiecrm.com/help-centre/client-portal-overview)Configure GDPR and consent purposes (https://pixiecrm.com/help-centre/configure-gdpr-and-consent-purposes)QR Code Compliance module overview (https://pixiecrm.com/help-centre/qr-code-compliance-module-overview)Email Marketing & Newsletter module overview (https://pixiecrm.com/help-centre/email-marketing-newsletter-module-overview)