• Core (out-of-the-box):
  Where a core, pre-existing trigger event exists, the development team has provided the system name, which appears here. The notification type is then automatically linked to the trigger event, and a notification of this type will be generated when the event occurs.
• Custom:
  If custom notification types are required, a new notification type can be created here and then called from a Visual Workflow. The Visual Workflow can be run from any triggered event.

This is what the user sees as the notification message's title and body. Take note of the following two points:
 

• The text of the title and message can be amended if required and a combination of text and tags can be used.
  
  Use the icon to access the Context Browser and select the required tags.
  
  Where tags for the specific work item are required (for example, to present the Title of the parent Matter), use the Work Item type and select the work type required. For example:
  
  
  Some core notifications may have pre-existing tags for key data. For example:
  
  These can be replaced with tags from the context browser if required. For example, in this case, Sharedo_Type_Name can be replaced with the tag notificationType.name
   
• Some core notifications have the Title and Message set automatically. 
  For example, in the Mentioned in comment notification type the Title is replaced by “<Name of User>  tagged you in a comment on <Title of Work Item>”, and the body is the actual comment that was made. Notification types where these are set automatically look like this:
  
  
   

This list is maintained in an Option Set and is used to dynamically build and group together the notification settings presented to the user. For example, if the category is Documents, then the various settings relating to documents are grouped and shown.

This determines the priority of the notification and the colour in which it is displayed to the user. For example, a critical priority is shown with a red mark.

The Priority and Notification Category are both displayed in columns on the Notification Types page in Admin. 

Additionally, the items in these two lists (Priority and Notification Category) are maintained in Option Sets and managed using the Option Sets subfeature, located within Modeller > Global features > Notifications.

Determines whether the user can override the delivery method within their notification settings (click on their profile at the top right of the ShareDo screen and select Notification Settings).
For example, a user might prefer not to be notified when a Document Bundle finishes or fails to generate (or may wish to alter the delivery method for this event from App to Email). They can do this through their notification settings.

However, a system administrator can prevent the option from appearing in the user's notification settings by toggling User Configurable to off.

Where this is applied, a filter icon appears next to the Notification Type for each user’s Notification Settings.

Clicking on the icon opens a blade that allows the user to filter notifications by a work type path or specific work types. For example: Restrict notifications for the Document Generation Failed type to only the Residential Purchase and Sale work types.

• When the Task is Completed 
  Suppose a notification fires when a task is progressed (for example, from New to In Progress). In that case, the notification will automatically expire if the task is subsequently completed, as it is no longer relevant, even if the Auto Expiry date has not been reached.
• Assigned to User
  Similarly, if a notification has been sent to the user for a specific task, but then the task is re-assigned to another user, the notification will automatically expire.