Configure the Letter Manager PDF logo
Use the CRM company logo shown in the top-left PDF header.
Exact navigationAdmin Area → Setup → Settings → Company Information / Branding
Before you begin
- 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 covers
Use the CRM company logo shown in the top-left PDF header. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.
Exact step-by-step process
- Upload or select the company logo in the CRM settings.
- Confirm the company_logo option points to a file under uploads/company.
- Generate a test letter.
- Verify the logo is rendered in the PDF header.
Fields, choices and supported possibilities
Action scopeUse the CRM company logo shown in the top-left PDF header.
Module version1.0.0
Exact routeAdmin Area → Setup → Settings → Company Information / Branding
EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow.
Code-backed validations and workflow rules
- The PDF Header checks uploads/company/{company_logo}.
- If the file does not exist, the image is not rendered.
Expected result and verification
- 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.