Notifications are automated emails or SMS messages sent when specific events occur in your program. For example, users can be notified when they submit an application or when an action stage starts.
Default notifications are included, but you can customise or create your own.
Create a notification
- In the Manage workspace, go to Settings > Communications > Notifications
- Click New notification
- Select a Trigger
- Set a legal basis for sending the message
- Provide a Description (optional)
- Choose categories (if applicable)
- Set recipients
- User: the person related to the event
- These email addresses: specified emails separated by commas or semicolons
- The address specified in this field: from an application field
- Add a Sender name and Reply-to email address (optional)
- Write the Email subject and Email body including merge fields as needed
- Click Save
Edit a notification
- In the Manage workspace, go to Settings > Communications > Notifications
- Click the notification subject
- Make your changes
- Click Save
You can also toggle notifications on or off using the active slider.
Available triggers
Available triggers may vary by plan.
| Trigger | Action |
| Action stage completed | Triggered when an action stage is completed (a 'Proceed' or 'Stop' decision is made). The notification must be selected on the action stage before being triggered. Learn more: Action flow configuration. |
| Actions stage started | Triggered when an action stage is started. The notification must be selected on the action stage before being triggered. Learn more: Action flow configuration. |
| Application eligible | Triggered when an application is found to be eligible. Learn more: Configure an eligibility screener. |
| Application ineligible | Triggered when an application is found to be ineligible. Learn more: Configure an eligibility screener. |
| Application invited | Triggered when a user is invited to complete an application from Users in the Manage workspace. |
| Application moderated | Triggered when an application is moderated (Approved, Rejected, or Undecided). Learn more: Moderation explained. |
| Application pending eligibility assessment | Triggered when an application is awaiting manager approval in in a manual eligibility screener. Learn more: Configure an eligibility screener. |
| Application resubmission required | Triggered when an application is flagged for resubmission. Learn more: Application resubmission. |
| Application resubmitted | Triggered when an application is resubmitted by the applicant or a manager. Learn more: Application resubmission. |
| Application submitted | Triggered when an application is successfully submitted by the applicant or a manager. |
| Application tagged | Triggered when an application is tagged. Learn more: What are tags? |
| Assignment completed | Triggered when a reviewer completes a reviewing assignment. |
| Assignment created | Triggered when reviewers are paired with applications via Applications in the Manage workspace. Learn more: Assign reviewers via the Applications view. |
| Collaborator invited | Triggered when an applicant invites a contributor to work on an application. Learn more: Collaborative submissions. |
| Document created | Triggered when a document is assigned to a user or application. Learn more: Documents and document templates. |
| Grant report due | Triggered before, after, or when a grant report is marked due based on all or selected grant statuses. Learn more: Grant reporting. |
| Grant report scheduled | Triggered when a grant report has been scheduled with a due date in the future. Learn more: Grant reporting. |
| Grant report submitted | Triggered when a grant report has been submitted by an applicant. Learn more: Grant reporting. |
| Grant status changed | Triggered when an application's grant status has been changed (Closed, In progress, Fully allocated, etc). Learn more: Grant status. |
| Order payment pending | Triggered on application submission when the applicant selects the invoice option. |
| Order payment success | Triggered on application submission when a payment succeeds via your payment gateway. |
| Payment due | Triggered when a scheduled payment is marked as due. Learn more: Payment tracking. |
| Payment status changed | Triggered when the payment status for an application has been changed. Learn more: Payment tracking. |
| Role granted | Triggered when a role is assigned to a user. Learn more: Assign or remove user roles. |
| User invited | Triggered when a user is invited to the platform. |
| User registered | Triggered when a user registers successfully. |
Troubleshooting notifications
If users are not receiving notifications:
- Check spam or junk folders
- Ask users to allow emails from no-reply@app.goodgrants.com and sender@app.goodgrants.com
- Check user preferences in Users
Good to know
- You can create multiple notifications for the same trigger.
- Only email is sent if both email and mobile are available.
- SMS messages are limited to 160 characters.
- The sender email address cannot be changed (for deliverability).
- Merge fields for multi-line content should be placed on their own line.
- Notifications can be configured per language for multi-language programs.
FAQs
Can I bypass user notification preferences?
Yes. You can set the legal basis when creating a notification. Always confirm compliance with local data laws before doing so.
Can I link to documents?
Yes. Link to publicly accessible documents. If password protected, include access details.
Can I customise sender details?
You can set a sender name and reply-to address. The sending address cannot be changed.
Can I use notifications in multiple languages?
Yes. Configure notifications for each enabled language
Can I add CC or BCC recipients?
No. Instead, duplicate notifications and assign different recipients.