Complete Letter Manager signer details
Enter the first name, last name and email collected with the signature. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goPublic signature page → Sign Document
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 you’ll accomplish
Enter the first name, last name and email collected with the signature. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.
Follow these steps
- Enter First Name.
- Enter Last Name.
- Enter Email Address.
- Verify the values identify the person signing.
- Continue to the signature pad.
Fields and options to review
Action scopeEnter the first name, last name and email collected with the signature.
Module version1.0.0
Exact routePublic signature page → Sign Document
EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow.
Rules the system enforces
- The view marks all three inputs required.
- The controller stores acceptance_firstname, acceptance_lastname and acceptance_email.
- The server action does not define additional format/business validation beyond the input helper filtering.
How to confirm 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.