In-App Notifications

In-app notifications tell dashboard users when something on an application needs their attention. Examples: a teammate assigns them an application, a borrower uploads documents or replies to a message, or someone mentions them in a note.

Notifications appear under the bell in the dashboard header and, as they arrive, as short pop-up toasts. They are personal: each user sees only their own. They are separate from the emails and SMS messages you send to applicants (see Email and SMS Templates).

Key concepts

• Recipient: the dashboard user the notification is for. For most application events, this is the user currently assigned to the application.
• Actor: the person whose action caused the notification. You are never notified about your own actions, except for the two "self" types below.
• Unread: new notifications are unread and count toward the badge on the bell.
• Batching: bursts of similar events on the same application are merged into one notification instead of many.
• Toast: a brief pop-up shown when a notification arrives. You can turn toasts off without turning off notifications.

Notification types

In the titles below, Teammate stands for the name of the person who took the action.

Notifications that depend on "the assignee" are only created when the application has an assigned user. Unassigned applications don't generate them.

Get notified when a stage is reached

To be notified when applications reach a particular stage (for example "Doc Received"):

1. Go to Settings → Workspace.
2. In the stages list, switch on Notify for the stage.

From then on, whenever an application moves into that stage, its assignee is notified, unless they made the change themselves.

Work with notifications

Read and clear notifications

1. Click the bell to open the Notifications panel. Notifications are grouped into Today, Yesterday, This week and Earlier, newest activity first. Unread ones are marked.
2. Click a notification to go straight to the relevant place: the application, its notes, tasks, documents or conversation. Opening a notification marks it as read.
3. Click Mark all as read to clear the badge.

📘

All caught up

When everything has been read, the panel shows You are all caught up.

Batching

Some events tend to arrive in bursts, so LendAPI merges them:

• Document uploads on the same application are combined into one notification, for example "3 documents uploaded, ready for review".
• Borrower messages (SMS and email together) on the same application are combined, for example "4 new messages from borrower", with the latest message as the preview.

A new event is merged into an existing notification if that notification was created in the last 15 minutes. After that, the next event starts a new notification. When an event is merged into a notification you had already read, it becomes unread again and moves to the top.

All other notification types are never batched. Each event creates its own notification.

Real-time updates

New notifications appear in the panel and as a toast while you are signed in, without refreshing the page. Use the toast button in the Notifications panel header (Turn off notification toasts / Turn on notification toasts) to silence pop-ups. Your choice is saved to your user profile, and the bell and panel keep working either way.

Notifications are never shown on borrower-facing pages, such as the application wizard or contract signing pages, even if a team member is signed in on the same browser.

Sub-tenants and environments

• Notifications are always limited to your own account. Users only see notifications addressed to them.
• Users who belong to a sub-tenant see notifications for applications they are assigned to, even though those applications belong to the parent tenant.
• Sandbox and Production keep separate notifications. Switch the environment selector in the header to see the other environment's notifications. See Sandbox and Live.

Reference

Use it via the API

Notifications are a dashboard feature for signed-in users. They have no public API and you can't create custom notification types. To react to application events in your own systems, use Webhooks.

Permissions

Every dashboard user can see their own notifications. There is no separate permission to grant. However, a notification only links somewhere useful if the user's role can open that part of the application. For example, a user without access to the Notes tab can't open a mention. See Roles and Permissions.

Best practices

• Assign applications. Most notifications go to the application's assignee. Unassigned applications produce few notifications.
• Use Notify on a few key stages only, such as the stage where documents are received or a file is ready for underwriting. Turning it on for every stage creates noise.
• Use @mentions in notes to pull a teammate into an application instead of messaging them outside LendAPI. The mention links directly to the note.
• Turn toasts off, not notifications, during focused work. Your unread badge still collects everything.

Related guides