Understand supported enclosure file types | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/understand-supported-enclosure-file-types Publisher: Pixie Technologies LLC Email delivery, attachments and read receipts Understand supported enclosure file types Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Follow this guide to use only extensions accepted by the upload helper. Audience: CRM staff; Permission: Authenticated staff account; Module v1.0.0; Where to goAdmin Area → Letter Manager → Enclosed File / Additional Email Attachment 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 Use only extensions accepted by the upload helper. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow. Follow these steps - Select PDF, PNG, JPG, JPEG, DOC or DOCX. - Avoid renamed executable or unsupported archive files. - Send a controlled test and verify the stored MIME/type. Fields and options Action scopeUse only extensions accepted by the upload helper. Module version1.0.0 Exact routeAdmin Area → Letter Manager → Enclosed File / Additional Email Attachment 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 server checks the lowercase filename extension against pdf, png, jpg, jpeg, doc and docx. - The HTML accept attribute mirrors those formats but server extension checking remains authoritative. 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)Distinguish PDF content from the email cover note (https://pixiecrm.com/help-centre/distinguish-pdf-content-from-email-cover-note)Understand the generated PDF email attachment (https://pixiecrm.com/help-centre/understand-generated-pdf-email-attachment)Understand the Letter Manager enclosure size limit (https://pixiecrm.com/help-centre/understand-the-letter-manager-enclosure-size-limit)Understand enclosure storage and filenames (https://pixiecrm.com/help-centre/understand-enclosure-storage-and-filenames)Handle a skipped Letter Manager enclosure (https://pixiecrm.com/help-centre/handle-a-skipped-letter-manager-enclosure)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)