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
User Event | Meaning | In-app | Push | |
Download ready | Download of multiple selected items is ready | ✔️ | ✖️ | ✖️ |
Download failed | Download of multiple selected items failed | ✔️ | ✖️ | ✖️ |
File replaced | A file has been replaced with a new version | ✔️ | ✖️ | ✖️ |
Event - notify | Notification about an event | ✔️ | ✔️ | ✖️ |
Folder - notify | Notification about a folder | ✔️ | ✔️ | ✖️ |
Story - notify | Notification about a story | ✔️ | ✔️ | ✖️ |
Task - notify | Notification about a task | ✔️ | ✔️ | ✖️ |
Form comment | New comment in the chat section of a form | ✔️ | ✖️ | ✖️ |
Story comment | New comment in the chat section of a story | ✔️ | ✖️ | ✖️ |
Task comment | New comment in the chat section of a task | ✔️ | ✖️ | ✖️ |
Form comment direct mention | Someone has tagged you in the chat section of a form | ✔️ | ✖️ | ✖️ |
Story comment direct mention | Someone has tagged you in the chat section of a story | ✔️ | ✔️ | ✖️ |
Form comment reply received | Someone has replied to your comment in the chat section of a form | ✔️ | ✖️ | ✖️ |
Story comment reply received | Someone has replied to your comment in the chat section of a story | ✔️ | ✔️ | ✖️ |
Task comment reply received | Someone has replied to your comment in the chat section of a task | ✔️ | ✔️ | ✖️ |
Task approved | Task approved notification | ✔️ | ✔️ | ✖️ |
Task cancelled | Task cancelled notification | ✔️ | ✖️ | ✔️ |
Form submitted | Form submitted notification | ✔️ | ✖️ | ✔️ |
Task approved - chain | Multiple people had to approve a task, and the last person in the chain has approved it | ✔️ | ✖️ | ✖️ |
Form complete | The form is complete; no action is required | ✔️ | ✔️ | ✔️ |
Task complete | Task complete notification | ✔️ | ✔️ | ✖️ |
Task distributed | A task has been distributed to people | ✔️ | ✔️ | ✖️ |
Task forwarded | A task has been forwarded | ✔️ | ✖️ | ✖️ |
Group approval complete | Group is a choice of approval type; i.e. select a group, but only one of those people needs to approve it A member of group has approved | ✔️ | ✖️ | ✖️ |
Task rejected | Approver has rejected task and requested changes | ✔️ | ✔️ | ✖️ |
Task submitted | Task has been submitted | ✔️ | ✔️ | ✔️ |
Task cancelled | System event only, no notification | ✖️ | ✖️ | ✖️ |
Task reminder sent | Reminder has been sent about a task that is yet to be completed | ✔️ | ✔️ | ✔️ |
Event sent | Event has been sent | ✔️ | ✖️ | ✖️ |
Folder shared | Folder has been shared | ✔️ | ✖️ | ✖️ |
Story shared | Story has been shared | ✔️ | ✔️ | ✖️ |
Form shared | A form has been shared and made available in the forms library | ✔️ | ✔️ | ✖️ |
Story submitted for review | Submitter (i.e. someone without ‘distribute’ permission) has created a story to be reviewed/amended/sent | ✔️ | ✖️ | ✖️ |
Task submitted for review | Submitter (i.e. someone without ‘distribute’ permission) has created a task to be reviewed/amended/sent | ✔️ | ✖️ | ✖️ |
