Understand bulk postal selection scope | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/understand-letter-manager-bulk-selection-scope Publisher: Pixie Technologies LLC Postal delivery and bulk tracking Understand bulk postal selection scope Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Avoid assuming selection persists across AJAX pages or searches. Audience: CRM staff; Permission: Authenticated staff account; Module v1.0.0; Where to goAdmin Area → Letter Manager → Sent Letters History 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 Avoid assuming selection persists across AJAX pages or searches. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow. Follow these steps - Filter and open the page containing the intended records. - Select only visible rows. - Complete the bulk update before navigating or reloading. - Check every intended record afterwards. Fields and options Action scopeAvoid assuming selection persists across AJAX pages or searches. Module version1.0.0 Exact routeAdmin Area → Letter Manager → Sent Letters History EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow. Rules and limits - The dashboard re-renders rows after search/page requests and resets Select All. - Selections are DOM-based and are not retained across pages. 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)Record the date handed to courier (https://pixiecrm.com/help-centre/record-the-date-handed-to-courier)Bulk update postal details for selected letters (https://pixiecrm.com/help-centre/bulk-update-postal-details-for-selected-letters)Handle no letter selected for postal update (https://pixiecrm.com/help-centre/handle-no-letter-selected-for-postal-update)Understand postal update audit fields (https://pixiecrm.com/help-centre/understand-postal-update-audit-fields)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)