Understand Letter Manager identifiers and tokens | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/understand-letter-manager-identifiers-and-tokens Publisher: Pixie Technologies LLC Security, privacy, limitations and troubleshooting Understand Letter Manager identifiers and tokens Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Distinguish database ID, reference, unique verification code, signature hash, visible verification code and email-open token. Audience: Administrators and developers; Permission: Authenticated staff account; Module v1.0.0; Where to goAdmin Area → Letter Manager → Internal Full View; code-backed reference 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 Distinguish database ID, reference, unique verification code, signature hash, visible verification code and email-open token. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow. Follow these steps - Use ID only as the internal numeric record key. - Use reference_no for operational correspondence lookup. - Use unique_code for public verification URL. - Use hash for the public signature URL and signature filename. - Use random_verification_code for visible barcode/evidence. - Treat email_open_token as private tracking infrastructure. Fields and options Action scopeDistinguish database ID, reference, unique verification code, signature hash, visible verification code and email-open token. Module version1.0.0 Exact routeAdmin Area → Letter Manager → Internal Full View; code-backed reference EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow. Rules and limits - Each identifier has a separate purpose and should not be substituted. - Public links do not expire in this release. 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)Understand Letter Manager stored personal data (https://pixiecrm.com/help-centre/understand-letter-manager-stored-personal-data)Apply least privilege to Letter Manager (https://pixiecrm.com/help-centre/apply-least-privilege-to-letter-manager)Retain and delete Letter Manager evidence safely (https://pixiecrm.com/help-centre/retain-and-delete-letter-manager-evidence-safely)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)