Understand enclosure storage and filenames
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Trace the stored file while preserving the original safe display name.
Where to goInternal Full View → Enclosed Attachment; server → uploads/letter_manager/enclosures
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
Trace the stored file while preserving the original safe display name. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.
Follow these steps
- Go to Internal Full View and note the displayed name, MIME and size.
- Go to or download the enclosure when authorised.
- On the server, confirm the stored enclosure_{id}_{timestamp}_{hash}.{ext} file.
- Apply retention and access controls.
Fields and options
Action scopeTrace the stored file while preserving the original safe display name.
Module version1.0.0
Exact routeInternal Full View → Enclosed Attachment; server → uploads/letter_manager/enclosures
EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow.
Rules and limits
- Unsafe characters in the original basename are replaced with underscores.
- The database stores relative path, safe original name, MIME and actual file size.
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
Was this guide useful?Your response is stored only in this browser.