Email Notifications
goPost™️ can trigger a variety of email notifications to different users based on the type of activity, the Agency’s Email Notification Configuration, and the individual user’s Email Notification Settings.
Notifications triggered by events are sent as emails to the email address provided by the user.
To avoid missing critical information, we do not recommend unsubscribing from any notifications that are preselected since these are usually based on the portal’s initial configuration. Users can subscribe to additional notifications if desired.
goPost Notifications
The list of available notification options will vary based on the Agency's configurations. This is particularly true for the subset of project “Status Update…” notifications as some of these are based on whichever project statuses have been configured within e-PlanREVIEW®.
The table below provides the base list of notifications for which users may receive emails and how those emails are triggered.
Notification Type | Notification | Notification Recipient | Triggering Event |
|---|---|---|---|
Project - Data | Created | Admin | Project has been created. |
Updated | Admin | Project information has been updated by an applicant. | |
Deleted | Applicant | Project has been deleted by an applicant or internal staff member. | |
Contact Created | Admin, Internal User, and Applicant | Contact has been added to the project application by a user. | |
Contact Deleted | Admin | Contact has been removed from a project application by a user. | |
Contact Updated | Admin | Internal staff member has updated Contact information. | |
Document Uploaded | Admin | Document has been processed into goPost. (This does not mean that review has been performed on the document.) | |
Document Deleted | Admin | Document has been deleted after processing. | |
Document Version Created | Admin | New document version has been uploaded by an applicant and linked to an existing document. | |
Project - Status | Status Update Changed to Accepted* | Admin and Applicant | Agency staff acknowledge the project application is satisfactory and complete and will proceed with processing for review. |
Status Update Changed to Denied | Admin | Agency staff have determined the project application is inappropriate (such as incorrect jurisdiction or incorrect type of application) and it will not be accepted for review. | |
Status Update Changed to Intake | Admin and Applicant | Staff have set the project application status to ‘Intake’ to notify the Applicant that the project application is undergoing a completeness check. It has not yet been accepted for review. | |
Status Update Changed to Intake Hold* | Admin and Applicant | The project has been placed on hold by agency staff pending some action by the Applicant. | |
Status Update Changed to Payment Pending* | Admin and Applicant | Staff have set the project application status to ‘Payment Pending’ to notify the Applicant that they must provide confirmation of payment of application fees before it will proceed to review. | |
Status Update Changed to Pending | Admin and Applicant | The project application and documents have been submitted to the agency upon clicking SUBMIT. | |
Status Update Changed to Pending Link | Admin and Applicant | The project application and documents have been submitted to the agency as a revision to an existing project upon clicking SUBMIT and are awaiting staff to associate the applications. | |
Status Update Changed to Approved* | Admin and Applicant | Staff have set the project application status to ‘Approved’ after review has been completed. | |
Status Update Changed to Corrections Required/Resubmit* | Admin and Applicant | One or more plan review documents require changes or a requirement is missing. | |
EPR Project Status Update (Project Status linked from EPR) | Admin and Applicant | Additional Status notifications may exist based on the project status values configured by Admins in EPR. These project status notifications will usually end in a parenthetical such as “(For Permitting)” or “(For Design Review)” to denote that they originate from a list within EPR. These options will remain available as long as the corresponding status value exists within EPR. | |
goPost Portal | Package Ready* | Applicant | The project application review has been completed and a set of plans have been delivered either with markups (if resubmittal is required) or approval stamps (if the application has been approved) for download. |
User | Created | Admin and Applicant | An account is created. |
Password Changed | (No email sent out.) | A password has been changed. (No email sent out.) | |
Updated | (No email sent out.) | An account has been updated. (No email sent out.) | |
General | Failed to Push Documents to Back Office | Admin | goPost to EPR API call fails. |
Unable to Post This Project to Back Office | Admin | goPost to EPR API call fails. | |
Applicant Support Email | Admin | Applicant sends email via goPost Help > Message Intake Staff. |
It is recommended, at a minimum, users subscribe to the notifications marked with an asterisk ( * ) in the table above.
Subscribing to Email Notifications
Initial notification subscriptions are set by the Administrator during configuration.
To subscribe to additional notifications:
Click on your Username at the top right.
Select Email Notification Settings from the drop-down.
Make sure that Email notifications are turned on.
To subscribe, check the box next to the desired notification.
If you cannot make changes to Email Notification Settings, then modifications have been restricted by the Agency Admin.
The initial notification configurations, which apply to any new account created, can be updated from within the Settings > Email Notification page. Changes to default configuration will affect accounts created afterward but are not retroactive so existing accounts will not be updated.