Understand non-configurable public verification elements
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Recognise page elements not included in the Public Verification Fields checklist.
Where to goPublic verify page
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
Recognise page elements not included in the Public Verification Fields checklist. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.
Follow these steps
- Go to a verify page after clearing all configurable fields.
- Verify the page still identifies the issuing sender and shows the random verification code/status presentation.
- Assess whether the remaining public information meets policy.
Fields and options
Action scopeRecognise page elements not included in the Public Verification Fields checklist.
Module version1.0.0
Exact routePublic verify page
EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow.
Rules and limits
- Sender name and random verification code are rendered outside the configurable field list.
- The settings controller cannot hide those elements in the supplied 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
Was this guide useful?Your response is stored only in this browser.