Check workspace branding, PDFs and protected evidence
Generated letters, emails, public forms and PDFs use the active workspace’s configured identity and supported native services.
Before you start
Generated letters, emails, public forms and PDFs use the active workspace’s configured identity and supported native services.
Follow these steps
- Check the workspace company name, logo, contact information and mail identity through normal settings.
- Generate or open the intended document from the correct record.
- Compare its property/recipient reference with the source evidence.
- Check the original uploaded document separately from the generated PDF.
- Verify protected file access with the intended authorised role before relying on a shared journey.
Check it worked
The document uses the current workspace identity and the correct business record, while protected evidence remains restricted.
If something does not look right
Missing branding can produce a neutral module label. OCR depends on configured extraction support; PDF/ZIP/mail functions depend on their native services. Escalate the specific failing function with its record reference.
Questions and answers
Will the module borrow another tenant’s logo?
The module reads the active workspace’s branding; it does not select another tenant’s logo as a fallback.
Does OCR approve a certificate?
No. Extraction must be reviewed through the native evidence approval process.
Can I open evidence from an old upload path?
Use the supported source record/file route. SaaS tenants resolve evidence inside their own protected workspace storage; an administrator must investigate a missing migration or relationship.