Frontline Portal - Notification types
Updated
by
Leigh Hutchens
We've outlined various notification scenarios, categorizing them by event and their corresponding delivery methods: in-app, push notification, and email. Whether it's notifying assignees about events, stories, or tasks or ensuring compliance review completion is communicated, the table below provides a detailed breakdown of how each notification type operates across different channels.
Notifications
Event | Meaning | In-app | Push | |
Archive created | Your download is ready (multiple items selected for download in files dashboard) | ✔️ | ✖️ | ✖️ |
Archive failed | Your download failed (multiple items selected for download in files dashboard) | ✔️ | ✖️ | ✖️ |
Asset replaced | A file has been replaced with a new version | ✔️ | ✖️ | ✖️ |
Assignees notified events | Notification about an event | ✔️ | ✔️ | ✖️ |
Assignees notified folders | Notification about a folder | ✔️ | ✔️ | ✖️ |
Assignees notified stories | Notification about a story | ✔️ | ✔️ | ✖️ |
Assignees notified tasks | Notification about a task | ✔️ | ✔️ | ✖️ |
Comment created forms | New comment in the chat section of a form | ✔️ | ✖️ | ✖️ |
Comment created stories | New comment in the chat section of a story | ✔️ | ✖️ | ✖️ |
Comment created tasks | New comment in the chat section of a task | ✔️ | ✖️ | ✖️ |
Comment mention created forms | Someone has tagged you in the chat section of a form | ✔️ | ✖️ | ✖️ |
Comment mention created stories | Someone has tagged you in the chat section of a story | ✔️ | ✔️ | ✖️ |
Comment reply created forms | Someone has replied to your comment in the chat section of a form | ✔️ | ✖️ | ✖️ |
Comment reply created stories | Someone has replied to your comment in the chat section of a story | ✔️ | ✔️ | ✖️ |
Comment reply created tasks | Someone has replied to your comment in the chat section of a task | ✔️ | ✔️ | ✖️ |
Compliance approved tasks* | Task approved notification | ✔️ | ✔️ | ✖️ |
Compliance cancelled tasks* | Task cancelled notification | ✔️ | ✖️ | ✔️ |
Compliance submitted forms* | Form submitted notification | ✔️ | ✖️ | ✔️ |
Compliance chain review completed* | Multiple people had to approve a task, and the last person in the chain has approved it | ✔️ | ✖️ | ✖️ |
Compliance completed forms* | The form is complete; no action is required | ✔️ | ✔️ | ✔️ |
Compliance completed tasks* | Task complete notification | ✔️ | ✔️ | ✖️ |
Compliance created* | A task has been distributed to people | ✔️ | ✔️ | ✖️ |
Compliance forwarded* | A task has been forwarded | ✔️ | ✖️ | ✖️ |
Compliance group review completed* | Group is a choice of approval type; select a group, but only one of those people needs to approve it, and this indicates that has happened | ✔️ | ✖️ | ✖️ |
Compliance rejected* | When someone submits a task, the approver can request changes | ✔️ | ✔️ | ✖️ |
Compliance submitted tasks* | Task submitted notification | ✔️ | ✔️ | ✔️ |
Completions canceled tasks | System event, not relevant here | ✖️ | ✖️ | ✖️ |
Reminder created | Tasks only, a reminder has been sent out about a task that is yet to be completed | ✔️ | ✔️ | ✔️ |
Resource distributed events | Event has been sent | ✔️ | ✖️ | ✖️ |
Resource distributed folders | Folder has been sent | ✔️ | ✖️ | ✖️ |
Resource distributed stories | Story has been sent | ✔️ | ✔️ | ✖️ |
Resource distributed templates | A form has been sent and made available to you in the forms library | ✔️ | ✔️ | ✖️ |
Resource submitted stories | Submitter (role) someone without distribute permission has created a story for you to review/amend/send | ✔️ | ✖️ | ✖️ |
Resource submitted tasks | Submitter (role) someone without distribute permission has created a task for you to review/amend/send | ✔️ | ✖️ | ✖️ |
* These are all system events and not all indicate a notification will be received.
