Product Feature Guide
Table Of Contents
Search and Filter Notifications
Introduction
A notification is when the User that is assigned to an application is notified from the platform based on the notifications table below. Notifications are sent out via email and in app (notification bell in the top right corner of dashboard). The type of notification received is based on the action. Either both types of notifications will be sent or one or the other. In app notifications (Bell) can not be turned on or off but they can be muted. Email notifications can be managed by each user within their settings in the system. They can choose which email notifications to turn on or off. This guide includes a list of all actions with their corresponding notifications.
In app notifications and email notifications with the exception of Chat email notifications are immediate. Chat email notifications are every 30 minutes if the user mentioned in the chat has not opened the relevant chat within 30 minutes of being mentioned. If they have opened it up within 30 minutes, they will not get the chat email notification.
All email notifications are individual notifications. This means one email per notification. The one exception to this is Application Assignment that may include Task Notifications. When a new user is assigned to an application and tasks are assigned as a result, the tasks will be grouped into one email. Any subsequent tasks that may be assigned as a result of stage transition for example would be individual email notifications.
Notifications
In app notifications can be viewed in both the dashboard and the pipeline view. To view all notifications associated with your account, click on the notifications icon i.e. the bell icon in the navigation bar.
The notification bell displays a badge showing the number of unread items. Users will notice the bell in your company's branding color instead of dark gray, along with a counter indicating the unread notifications.
Note: In-app notifications will persist even if you have your email notifications turned off in your settings as they are independent functionalities.
By default, notifications are retained for a period of 30 days, which means they are automatically removed from the user’s view after this time. However, your organization has the flexibility to reconfigure this retention period to a duration of your choosing.
We have two distinct ways of displaying in app notifications. The default setting which every environment defaults to or the Updated In App Notifications setting which needs to be enabled at the client’s request.
Default Setting
With the default setting, when users click on the notification icon, they will see a list of unread notifications sorted in order of receipt, with the most recent notification at the top.
From there, users can action the notifications using one of the options described below:
Mark all as read: To mark all notifications as read, click on the notification bell and select the “Mark all as read” option. Marking a notification as read will leave the notification text in the list but the text color changes to a lighter version and the counter number will reduce.
❗ We are aware of an issue where marking all notifications as read does not persist when users log out of the application. When users log back into the application, some of the notifications revert back to being unread, and the counter reappears. This limitation is being addressed by our development team but there is no estimated time for a fix. As a temporary workaround, users have the following options:
- Utilize the “Mark as read” function for individual notifications.
- Don't log out of your system. There is no need now for you to log out of your system daily as originally recommended. So, if you use the Mark all as read option instead and do not log out, this will persist until you do logout.
This guide will be updated once the issue is resolved.
Clear all: To clear all notifications, click on the notification bell and select the “Clear all” option. Clearing your notifications will remove them from the list altogether and the counter indicator will disappear until the next notification appears. You cannot undo this action.
Mute: To mute notifications, click the notifications icon and select the “Mute” option. Muting notifications only prevents the notification pop-up from displaying. It does not stop the counter, the notification from appearing in the notification list, or the email notification if they are toggled on by the user.
Only Show Unread: You can filter notifications to only show those that are unread. To do so, click on the notification bell and select the “Only show unread” option. This will filter the notification list to display only the unread notifications, making it easier to manage and prioritize important notifications.
Additionally, there are options to manage individual notifications. When you hover over a notification, an ellipsis will appear. Click on the ellipsis to access options to mark the notification as read or unread, or clear the notification.
Mark as read: To mark a specific notification as read, click on the ellipsis (three dots) within the notification itself and select “Mark as read.” This will change the text color to a lighter version, indicating it has been read, and reduce the counter number.
Mark as unread: To mark a specific notification as unread, click on the ellipsis (three dots) within the notification itself and select “Mark as unread.” This will change the text color back to its original state and increase the counter number, indicating it is unread.
Clear Notification: To clear a specific notification, click on the ellipsis (three dots) within the notification itself and select “Clear notification.” This will remove the specific notification from the list entirely.
Updated In App Notifications
Due to the way users are added to a deal throughout its lifecycle and their reliance on notifications to stay informed, there is an opportunity to make the notification system more effective in allowing users to manage their workload. To address this, notifications should be grouped and filtered by specific criteria, ensuring users only see alerts relevant to their role and stage in the workflow. This provides a more organized and user-friendly experience.
Note: This is a tenant setting and is disabled by default. To enable this setting, please contact our Client Success Team.
Notifications are grouped by their associated application (e.g., deal), and the relevant deal stage. This ensures that all notifications related to a single application are displayed together. When users open the notifications list from the bell icon, they see a list of applications that have received notifications. These groups are collapsed by default and can be expanded to view the individual notifications within each application.
Each group displays relevant details such as:
- Borrower's Name
- Deal Number
- Current Deal Stage
- Loan Amount
- Notification Type (e.g. Application, Approval, Chat, Document, Insurance, Task, Warning, Document Request Note Created, etc.)
- When the notification was received
When multiple submissions are made for the same deal, they will be grouped into separate application groups for each submission. Each submission will have a different deal number, making it easier to differentiate between them.
The notifications are further sorted by when they are received, with the most recent notification appearing at the top. This applies to the overall notifications list, as well as each group of notifications per application. There is an option to expand and view additional notifications.
All comparisons should be done at the level of minutes. If two notifications are coming at the same time then they are going to be considered as being concurrent and the sorting will pick the first one as returned by what is stored in the backend.
Example:
- Michael Smith application has two notifications:
- Today at 11:00 AM (most recent)
- Today at 9:00 AM
- John Doe application has two notifications:
- Today at 10:30 AM (most recent)
- Today at 10:00 AM
Group Notifications by Time
Notifications are further categorized into the following groups:
- Today
- Yesterday
- Older
This is done at the group level, using the time from the most recent notification within that group.
Example:
- Michael Smith application has three notifications:
- One from today
- One from yesterday
- One from two days ago
Users see the Michael Smith application listed under the 'Today' group, even though it contains notifications from yesterday and two days ago. When the user expands the Michael Smith notification group, they can view all three notifications within it.
Search and Filter Notifications
- Search Bar: You can search notifications, making it quicker to find specific updates. It is important to note that you can only search by applicant name.
- Users can filter notifications based on the following criteria:
- Show Only Unread Toggle: enables the user to toggle on to display only unread notifications.
- Stages: Filters notifications by specific deal stages. These will vary based on the tenant’s configuration.
- Notification Type: Filters by the following types:
- Application
- Approval
- Chat
- Document
- Insurance
- Task
- Warning
- Document Request Note Created
- The Filter icon will display a counter badge indicating the number of active filters.
- Filters will persist even after refresh, and will be saved for future sessions, ensuring a consistent user experience across logins.
- The notification counter badge updates dynamically based on the applied filters. We have included tooltips to provide clarity on filtered vs. total notifications:
- When filters are applied, hovering over the bell icon displays:
- “11 filtered notifications (20 total).”
- When no filters are applied, hovering over the bell icon displays:
- “20 notifications.”
Notification Actions
Users have control over notifications with the following actions:
- For All Notifications:
- Mark All as Read
- Marks all received notifications as read.
- The notification count on the bell icon clears.
- Clear All Notifications
- Removes all received notifications.
- Users will no longer see these notifications, and the counter will clear
- Mute
- Temporarily disables all notifications from appearing in the list.
- Users will not receive alerts until they unmute notifications.
- Mark All as Read
- Notification Actions by Application:
- Mark All as Read
- Marks all notifications within a specific application group as read.
- The application group will remain in the list, but all notification items within the group will be grayed out.
- Mark All as Unread
- Marks all notifications within a specific application group as unread.
- Mark All as Read
- Notification Actions at Individual Notification:
- Mark as Read
- Marks a specific notification as read.
- The notification item is grayed out.
- Mark as Unread
- Marks a specific notification as unread.
- Mark as Read
Note: If a notification is marked as read then the option to mark it as unread is disabled, and vice versa.
- Clear Notification
- Removes the specific notification from the list.
Warning Notifications
With this updated display, we have also ensured that warning notifications are sent to assigned users on a deal. A good example of this is when the product applied on the deal is updated in the Manager Portal and may need to be re-applied.
Below is a table of all system notifications identifying the notification, how it is sent (in app and/or email), who it is sent to, and the general notification message.
Notifications Table
Category: Tasks
Action |
Notification Sent |
Who is notified |
Response Time |
Message |
New Task Assigned |
In-App |
Assigned User of the task |
Immediate |
Bell: Task Updated Your assigned task “task_name” has been updated on “primary_borrower_name” application. Email: Task Updated: “task_name” on “primary_borrower_name” application Hello user_name, Your assigned task “task_name” has been updated on “primary_borrower_name” application. Task: — Description: — Stage: — Priority: — Assignee: — Due Date: — Due Time: — Open Application |
Task Updated |
In-App |
Assigned User of the task |
Immediate |
Bell: Task Updated Your assigned task “task_name” has been updated on “primary_borrower_name” application. Email: Task Updated: “task_name” on “primary_borrower_name” application Hello user_name, Your assigned task “task_name” has been updated on “primary_borrower_name” application. Task: — Description: — Stage: — Priority: — Assignee: — Due Date: — Due Time: — Open Application |
Task Completed |
In-App |
Everyone who is assigned to the application |
Immediate |
Bell: Task Completed The task “task_name” has been completed on “primary_borrower_name” application. Email: Task Completed: “task_name” on “primary_borrower_name” application Hello user_name, The task “task_name” has been completed on “primary_borrower_name” application. Task: — Description: — Stage: — Priority: — Assignee: — Due Date: — Due Time: — Open Application |
Task Deleted |
In-App |
Everyone who is assigned to the application |
Immediate |
Bell: Task Deleted The task “task_name” has been deleted on “primary_borrower_name” application. Email: N/A |
Category: Application
Action |
Notification Sent |
Who is notified |
Response Time |
Message |
New user assigned |
In-App |
Assigned User of the task |
Immediate |
Bell: Application Assigned You have been assigned as role_name on “primary_borrower_name” application. Email: Application Assigned: “borrower_name” Hello user_name, You have been assigned as role_name on “primary_borrower_name” application. Open Application |
UW is auto assigned to application |
In-App |
Assigned User of the application |
Immediate |
Bell: Application Assigned You have been assigned as role_name on “primary_borrower_name” application. Email: Application Assigned: “borrower_name” Hello user_name, You have been assigned as role_name on “primary_borrower_name” application. Open Application |
Delegate is assigned (OOO) |
In-App |
Assigned Delegate |
Immediate |
Bell: Delegate Assignment You have been assigned as delegate for requester_name (role_name). Email: Delegate Assignment: “requester_name (role_name)” Hello user_name, You have been assigned as delegate for requester_name (role_name). |
Application stage change |
In-App |
Everyone who is assigned to the application |
Immediate |
Bell: Application Stage Change “primary_borrower_name” application has been moved from “old_stage” to “new_stage”. Email: Application Stage Change: “primary_borrower_name” application moved to “new_stage” Hello user_name, “primary_borrower_name” application has been moved from “old_stage” to “new_stage”. Open Application |
Duplicate application notification |
In-App |
Everyone who is assigned to the application |
Immediate |
Bell: Duplicate Found Similar application “primary_borrower_name_dup” to the one you have assigned “primary_borrower_name” has been created. Email: Duplicate Found: “primary_borrower_name_dup” Hello user_name, Similar application “primary_borrower_name_dup” to the one you have assigned “primary_borrower_name” has been created. Reason: — Comment: — table Open Application |
Application status changes Pending Approved |
In-App |
Everyone who is assigned to the application |
Immediate |
Bell: Application Approved/Pended ”primary_borrower_name” application has been approved/pended. Email: Application Approved/Pended: “primary_borrower_name” application Hello user_name, ”primary_borrower_name” application has been approved/pended. Open Application |
Locked or Unlocked |
In-App |
Everyone that is assigned to the application |
Immediate |
Bell: Application Locked/Unlocked ”primary_borrower_name” application has been locked/unlocked. |
Archive or Unarchive |
In-App |
Everyone that is assigned to the application |
Immediate |
Bell: Application Archived/Unarchived ”primary_borrower_name” application has been archived/unarchived. |
Deleted |
In-App |
Everyone that is assigned to the application |
Immediate |
Bell: Application Deleted ”primary_borrower_name” application has been deleted. |
Category: Approval
Action |
Notification Sent |
Who is notified |
Response Time |
Message |
Approval request updates |
In-App |
Requestor |
Immediate |
Bell: Request Approved/Declined approver_name has approved/declined your approval request “approval_type” on “primary_borrower_name” application. Changes Requested approver_name has requested changes on your approval request “approval_type” on “primary_borrower_name” application. Email: Request Approved/Declined: “approval_type” on “primary_borrower_name” application Hello requestor_name, approver_name has approved/declined your approval request “approval_type” on “primary_borrower_name” application. Comment: — Open Application Changes Requested: “approval_type” on “primary_borrower_name” application Hello requestor_name, approver_name has requested changes on your approval request “approval_type” on “primary_borrower_name” application. Comment: — Open Application |
Approval Requested |
In-App |
Approver |
Immediate |
Bell: Approval Requested requestor_name has requested your approval “approval_type” on “primary_borrower_name” application. Email: Approval Requested: “approval_type” on “primary_borrower_name” application Hello approver_name, requestor_name has requested your approval “approval_type” on “primary_borrower_name” application. Comment: — Open Application |
Category: Chat
Action |
Notification Sent |
Who is notified |
Response Time |
Message |
Chat mention |
In-App |
User mentioned in chat |
Immediate |
Bell: Mentioned in chat author_name has mentioned you in the chat on “primary_borrower_name” application. Email: Mentioned in chat on “primary_borrower_name” application Hello user_name, author_name has mentioned you in the chat on “primary_borrower_name” application. list of messages Open Application |
Category: Document
Action |
Notification Sent |
Who is notified |
Response Time |
Message |
Condition Document uploaded |
In-App |
Everyone that is assigned to the application |
Immediate |
Bell: Documents Uploaded Documents have been uploaded on “primary_borrower_name” application. Email: Documents uploaded on “primary_borrower_name” application Hello user_name, Documents have been uploaded on “primary_borrower_name” application. table (a list of documents) Open Application |
Condition Document reviewed |
In-App |
Everyone that is assigned to the application |
Immediate |
Bell: Document Accepted/Rejected ”document_name” has been accepted/rejected on “primary_borrower_name” application. Email: Document Accepted/Rejected: “document_name” on “primary_borrower_name” application Hello user_name, ”document_name” has been accepted/rejected on “primary_borrower_name” application. Comments: — Open Application . |
Condition Document comment added |
In-App |
Everyone that is assigned to the application |
Immediate |
Bell: New Comment on Document author_name added a new comment to document “document_name” on “primary_borrower_name” application. Email: New Comment on Document: “document_name” on “primary_borrower_name” application Hello user_name, author_name added a new comment to document “document_name” on “primary_borrower_name” application. Comments: — Open Application |
Category: User
Action |
Notification Sent |
Who is notified |
Response Time |
Message |
Create a new user |
|
Target user |
Immediate |
Welcome to fundmore.ai Hello, Here is your username user_name and here is your temporary password password Please use the above credentials to login into dev.fundmore.ai All the best, The fundmore.ai Team |
Forgot Password |
|
Target User |
Immediate |
Your fundmore.ai verification code Hello, Your fundmore.ai verification code is code_number. |
Category: Integrations
Action |
Notification Sent |
Who is notified |
Response Time |
Message |
Insurance quote updated |
In-App |
Everyone who is assigned to the application |
Immediate |
Bell: Mortgage Insurance Quote Updated Mortgage insurance quote #insurance_number has been updated on “primary_borrower_name” application. Email: Mortgage Insurance Quote Updated: #insurance_number on “primary_borrower_name” application Mortgage insurance quote #insurance_number has been updated on “primary_borrower_name” application. Open Application |
Insurance quote updated |
In-App |
Everyone who is assigned to the application |
Immediate |
Bell: CMHC MI Quote Updated CMHC MI quote #insurance_number has been updated on “primary_borrower_name” application. Email: CMHC MI Quote Updated: #insurance_number on “primary_borrower_name” application CMHC MI quote #insurance_number has been updated on “primary_borrower_name” application. Latest status: — Open Application |
Insurance quote updated |
In-App |
Everyone who is assigned to the application |
Immediate |
Bell: Sagen MI Quote Updated Sagen MI quote #insurance_number has been updated on “primary_borrower_name” application. Email: Sagen MI Quote Updated: #insurance_number on “primary_borrower_name” application Sagen MI quote #insurance_number has been updated on “primary_borrower_name” application. Latest status: — Open Application |
There are additional notifications available for other functionalities which are documented within the relevant Product Feature Guides. See relevant guides below: