TABLE OF CONTENTS
Summary
Configuring your notification settings in Source is essential to ensure you and your team never miss an important update. Whether through in-platform alerts or email notifications, you can customise how and when you’re notified of key case activity, reviews, and changes. Email notifications are grouped and scheduled to reduce inbox noise, helping you stay focused and responsive without being overwhelmed.
Notifications
Source supports two delivery channels for notifications:
Platform notifications: Alerts appear in the Source interface when you're logged in.
Email notifications: Alerts are sent to the user’s registered email address.
Email notifications are automatically grouped to avoid spamming users.
If multiple notifications occur in a short period, they will be bundled into a single email summary.
Email notifications are also useful so that you do not need to log in to check if you have action items.
Setting Up
To configure your notification preferences:
Go to Settings > Notifications in the left-hand navigation bar.
Locate the notification you'd like to configure (e.g., Case status change - Ready for Review).
Click the three dots on the right and select "Edit".
Choose your preferred delivery methods:
Send notification (used for integrations or system processing)
Send platform notification
Send email notification
Set recipients using Case Role (e.g., Case Lead, Case Requester, Assigned Users) or select specific Platform Users.
Click Save.
If you're sending notifications via email, you'll also need to set:
Frequency:
Quarter-hourly
Half-hourly
Hourly
Twice daily (9:00am & 1:00pm)
Daily (9:00am)
The 9am and 1pm times are based on the below time zones:
• Australia – Sydney time
• United Kingdom – London time
• New Zealand – Auckland time
Notification Types Explained
| Notification | Received when |
|---|---|
| Advanced source of funds received | When the customer submits their advanced source of funds form. |
| Auto-unwrap completed | Entity unwrapping has successfully completed automatically. |
| Auto-unwrap unable to continue | Auto-unwrapping failed to complete - manual action may be required. |
| Case status change – Abandoned | A case has been marked as abandoned. |
| Case status change – Completed | The case has been completed and AML verification is finalised. |
| Case status change – Created | A new case has been created. |
| Case status change – Ready for Review | The case has reached Ready for Review status. |
| Conversation mention | A user has been @mentioned/tagged in a conversation within a case. |
| Electronic identification verification form received | A customer has completed and submitted their electronic ID form. |
| Email bounce | A notification email failed to deliver to a user. |
| Entity unwrap failure | An attempt to unwrap an entity structure has failed. |
| Entity unwrap success | An entity unwrap has successfully been completed. |
| Exception added (entity) | An exception has been added to an entity in the case. |
| Exception added (individual) | An exception has been added to an individual in the case. |
| Exception deleted (entity) | An exception has been removed from an entity. |
| Exception deleted (individual) | An exception has been removed from an individual. |
| Manual activity log entry added | A user has manually added an entry to the activity log. |
| New case note | A new case note has been added to the case. |
| Requirement received | A requested document or requirement has been submitted by the customer. |
| Review requested – case | A user has been requested to review the case. |
| SMS error | A failure occurred while attempting to send an SMS to the customer. |
Recommended Notifications to Send via Email
While each organisation will have its own workflow and preferences, there are a few key notifications we recommend considering for email delivery instead of relying solely on in-platform alerts.
These notifications are typically high-signal and time-sensitive - meaning users may benefit from seeing them even when they're not logged into Source.
Suggested Notifications to Set to Email:
- Electronic identification verification form received
Be alerted as soon as a customer has completed their ID verification so the case can progress without delay. - Requirement received
Know immediately when supporting documentation (e.g. proof of address, company documents) is received, so you can continue processing the case. - Review requested – case
Ensure reviewers are aware they have an action waiting. This is especially helpful when reviews are time-sensitive and part of a layered approval workflow. - Conversation mention
When a user is tagged in a note or discussion, email delivery ensures they don’t miss the context or request — especially useful if Source isn’t always open. - Case status change – Completed (send to Case Lead)
This is helpful when the case lead is responsible for follow-up actions once AML verification is complete. Email notification keeps them informed in real time so they can proceed without delay.
These settings can be configured per notification but only at a platform level not user specific, including selecting the frequency and recipient(s) to match your internal responsibilities and response expectations.
FAQs
If I select email will I receive every notification as an email?
Source automatically groups notifications during the same timeframe into one email to prevent inbox overload, however if you select real time then you will receive every notification as an email and this might be useful depending on the notification type.
Who can receive email notifications?
You can target:
- Case Requester
- Case Lead
- Assigned Users
- Specific Platform Users (e.g., your admin team)
This allows flexible coverage - even when the assigned user is unavailable.
What happens if I change the notification type?
Changes to notification do not apply retroactively. This is important to keep in mind that if you update from one type of notification to another you may still receive the old type for a short period of time.
Can notifications go to non-platform users?
Yes, they can. You can enter the name and email of a non-platform user manually into the Case Lead section within the case.
However, since non-platform users don't have access to the Source interface, some notifications won't be relevant or actionable for them — for example, a platform-only alert or a review request.