Understand recipient deduplication
Prevent the same email address receiving duplicate copies.
Exact navigationLicence Applications notification process
Before you begin
- Use the exact navigation above and confirm the intended invoice, case, client, property, document or environment.
- Confirm 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 this guide covers
Prevent the same email address receiving duplicate copies. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Exact step-by-step process
- Open 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, choices and supported possibilities
Deduplication keyEmail address
Category/help-centre/category/licence-applications/
Topic/help-centre/topic/licence-applications-notifications-audit/
Code-backed validations and workflow rules
- The model records email outcomes in audit evidence and does not roll back the case transaction solely because email fails.
Expected result and verification
- Understand recipient deduplication 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.