Purpose Statement
This enhancement introduces new configuration options that allow administrators to control whether permit contacts receive email notifications when a permit status changes.
With this update, agencies will have greater flexibility over permit communication behavior, including separate handling for permits created through CC/HH/BP-originated workflows.
Note: This functionality will be available with the upcoming new UI release. Once released, this functionality will automatically be available to all agencies.
Background Information
Currently, permit contacts automatically receive email notifications whenever a permit status changes. THIS BEHAVIOR IS NOT CONFIGURABLE.
As part of the new UI enhancements, two configurable options will be introduced under Permit Type > Options, allowing agencies to control when these notifications are sent.
This enhancement supports two notification paths:
- General permit status change notifications for standard permits
- CC/HH/BP-specific status change notifications for permits created through those originating sources
Once the new UI is released, these settings will fully control notification behavior at the Permit Type level.
Required Permissions
Users must have permission to:
- View and edit Permit Types
- Access the Options section within Permit Type configuration
- Save administrative configuration changes related to permit behavior
Step-by-Step Guide
1. Navigate to Permit Type Options
Go to the Permit Type configuration area and open the Options section for the desired Permit Type.
2. Configure General Notification Setting
Locate the setting:
Notify permit contact on status change
- Default: OFF (NO)
- When enabled, permit contacts will receive emails for status changes on standard permits
3. Configure CC/HH/BP Notification Setting
Locate the setting:
Notify permit contact on status change (CC/HH/BP permits only)
- Default: ON (YES)
- Applies specifically to permits created via CC/HH/BP
4. Save Configuration
Click Save to apply changes to the Permit Type.
5. Verify Notification Behavior
Test permit status changes using different permit origins to confirm the settings behave as expected.
Best Practices
- Review notification settings after the new UI release to ensure desired behavior
- Use Permit Types strategically to control communication for different workflows
- Test both standard and CC/HH/BP-originated permits after configuration changes
- Communicate changes to staff so they understand when contacts will (or will not) receive emails
Troubleshooting & FAQs
Will this change immediately affect my current notifications?
No. The updated behavior will take effect once the new UI is released.
Why is a permit contact still receiving emails when general notifications are disabled?
If the permit was created via CC/HH/BP, the CC/HH/BP-specific setting may still be enabled, which allows emails to be sent.
Why is a CC/HH/BP permit not sending an email?
Check the CC/HH/BP-specific notification setting. If it is disabled, emails will not be sent unless the general notification setting is enabled.
What happens if both settings are enabled?
Emails will be sent for all permit status changes, regardless of origin.
What are the default values?
- Notify permit contact on status change = OFF (NO)
- Notify permit contact on status change (CC/HH/BP permits only) = ON (YES)
Use Case Examples
Standard permit with general notifications disabled
A status change occurs on a standard permit. No email is sent.
Standard permit with general notifications enabled
A status change occurs on a standard permit. An email is sent to the permit contact.
CC/HH/BP permit with general disabled and CC/HH/BP enabled
A status change occurs. An email is sent due to the CC/HH/BP-specific setting.
CC/HH/BP permit with CC/HH/BP disabled and general enabled
A status change occurs. An email is sent due to the general setting.