Overview
SwiftComply Stormwater sends notifications when things change at the sites you're associated with: deficiency level changes, deficiencies that pass their due date, missing reports, qualifying precipitation events, and similar events. Each user controls which of these they receive and how (system notifications, email, or both).
This article also covers custom email templates, which let you standardize the messages you send out from SwiftComply.
Administrators cannot change notifications on behalf of another user. Each user sets their own preferences.
Managing your notifications
Use the Notification Manager to choose which site-level events you get notified about and how those notifications are delivered.
Click the Settings (gear icon) in the upper right corner, then select Manage Notifications.
You'll see a list of notification types that fire when changes happen at the sites you're associated with.
For each notification type, toggle how you want to be notified:
System Notifications: appears in the in-app notification panel.
Email Notifications: sent to your registered email address.
You can turn either or both on for each notification type, or turn both off to stop receiving that notification entirely. Changes save as you toggle.
Notification types
Common notification types in SwiftComply Stormwater include:
Location Status Change: when a site's operational status changes.
Deficiency Level Change: when a deficiency's severity level is updated.
Deficiency Past Due: when a deficiency passes its due date without being resolved.
Missing Report: when a required report isn't submitted by its deadline. Only fires if Time-Based Reporting Requirements are configured by the SwiftComply team.
Qualifying Precipitation Event: when a precipitation event meets the regulatory threshold at a site you're associated with.
The exact list shown in your Notification Manager depends on which programs are enabled on your account.
Custom email templates
Custom email templates let you standardize outgoing communications, for example inspection follow-up emails or violation notices.
Creating a template
Click the Settings (gear icon) in the upper right corner, then go to My Custom Preferences > Custom Email Templates.
Click to add a new template.
Fill in the fields:
Title: the template name.
Subject: the email subject line.
Body: the email content. Use merge fields like
{{recipient_name}}and{{recipient_email}}for dynamic content.
Click Save.
Using a template
When sending an email from SwiftComply (for example, emailing a deficiency or a report), select one of your saved templates to prefill the subject and body.
Viewing the email log
Click Communications in the left sidebar.
Click Email Log.
View all sent emails with dates, recipients, and delivery status. Filter by date range, recipient, or type.
The email log is a complete audit trail of system-generated and user-sent emails.
FAQ
Q: Can an administrator change notifications for another user?
A: No. Each user controls their own notification preferences from Manage Notifications. Administrators can add and deactivate users, but they cannot toggle notifications on someone else's behalf.
Q: Why aren't I receiving Missing Report notifications?
A: Missing Report notifications only fire when Time-Based Reporting Requirements are configured for your account. These are set up by the SwiftComply team; contact your representative if you need them enabled.
Q: Can I turn off all notifications?
A: Yes. In Manage Notifications, toggle off both System Notifications and Email Notifications for every notification type. You'll stop receiving in-app and email alerts.
Q: I don't see all the notification types listed in this article. Why?
A: The notification types shown to you depend on which programs are enabled on your account and your role. If a notification type isn't listed in your Manage Notifications page, your account isn't configured for that event type.
Q: What merge fields can I use in custom email templates?
A: Global merge fields include {{recipient_name}} and {{recipient_email}}. Additional merge fields may be available depending on context (for example, deficiency-specific fields when emailing a deficiency).