Settify allows your firm to control who receives specific types of email notifications – such as new client submissions, intake updates, and platform announcements – ensuring the right people stay informed.
The steps differ slightly depending on whether your firm is using the Legacy or Next Gen platform.
How to Review & Update Notification Recipients
Legacy Platform
Go to ‘Configure Settify’
Select ‘Customise the admin experience’
Scroll to the Notification Settings section
Next Gen Platform
Click ‘Settings’ at the bottom of the left-hand menu
Select ‘Admin facing’
Scroll to the Notification Settings section
Notification Fields Explained
When updating your settings, here are the key fields you'll encounter and what they control:
Field Name | What It Does |
---|---|
Email addresses to be CCed on new lead notifications, but not on any other Settify emails | Add staff here to receive alerts for new client submissions only (no other notifications). Useful for intake teams or admin inboxes. |
Email address for Settify notifications | The primary email address where all Settify platform notifications will be sent. This should be monitored regularly. |
CC addresses for Settify notifications | Secondary recipients of Settify notifications – these users will receive the same updates as the primary contact |
Key relationship contacts | People listed here will receive important announcements and service updates (e.g. new features, billing changes, maintenance alerts). This is typically suited to management or key decision-makers. |
Tips & Recommendations
Ensure your primary Settify notification email is regularly monitored.
Use a shared inbox like
intake@yourfirm.com
where relevant.Include at least two team members in key fields to ensure coverage.
Review your settings after staffing changes or every few months.
Need Help?
Not sure which version you're using or need assistance updating these fields? Reach out to our support team – we're always happy to help!
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article