Recognise the document-added email subject
Identify staff or client document events. 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 goEmail inbox → Licence Application Document Added {reference}
Before you start
- Use the exact navigation above and confirm the intended invoice, case, client, property, document or environment.
- Verify module activation and the stated permission before attempting the action.
- Use a controlled test record for payments, emails, public/portal access, provider calls and deletion.
What you’ll accomplish
Identify staff or client document events. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Follow these steps
- Go to the relevant case or email settings.
- Identify the trigger, recipient, subject or audit event described.
- Correct contact or SMTP configuration where needed.
- Use a controlled new action only after confirming the original record was already saved.
Fields and options to review
Subject prefixLicence Application Document Added
Category/help-centre/category/licence-applications/
Topic/help-centre/topic/licence-applications-notifications-audit/
Rules the system enforces
- The model records email outcomes in audit evidence and does not roll back the case transaction solely because email fails.
How to confirm it worked
- Recognise the document-added email subject completes through the supplied module flow.
- Reopen the source record or settings page and verify the stored value, status, payment, file, timeline entry or notification.
Security, privacy and operational checks
- Use the least-privilege account that has the stated permission.
- Use a controlled test record before applying provider, financial, public-link, email or destructive actions in production.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.