Notification Channels

Nembl's notification system keeps everyone informed as work moves through the platform. This guide explains the types of notifications you will encounter, how each channel works, and how to manage the flow of information.

How Notifications Work

Whenever something happens that affects you in Nembl, the system generates a notification. Events that trigger notifications include:

• A request you submitted changes status.
• A task is assigned to you.
• Someone comments on a request you are involved in.
• A workflow phase needs your approval.
• An item arrives in your inbox.
• A task is overdue.

Each notification is delivered through the channels you have enabled in your preferences. See Notification Preferences to configure your settings.

Notification Types

Nembl generates different types of notifications depending on the event:

Request Notifications

These keep requesters and stakeholders informed about request progress:

• Request accepted — Your request has been picked up by a team or individual.
• Request status changed — The request moved to a new phase or state.
• Request completed — Your request is done and the work has been delivered.
• Request rejected — Your request was not accepted, with a reason provided.
• Request cancelled — The request was cancelled by you or an administrator.
• Comment added — Someone posted a comment on a request you are following.

Workflow Notifications

These alert people when workflows need attention:

• Approval needed — A workflow phase requires your approval to proceed.
• Phase started — A new workflow phase has begun that involves you.
• Phase completed — A phase you were involved in has finished.
• Workflow stuck — A workflow has been in the same phase for an unusually long time (sent to administrators).

Task Notifications

These help task assignees and managers stay on top of work:

• Task assigned — A new task has been assigned to you.
• Task reassigned — A task was moved from you to someone else, or vice versa.
• Task completed — A task on a request you own or follow has been completed.
• Task overdue — A task has passed its due date without being completed.

Escalation Notifications

These flag situations that need immediate attention:

• Overdue task — A task has missed its deadline.
• Stuck request — A request has not progressed in an unusual amount of time.
• Capacity warning — An inbox or team has more pending items than usual.
• Agent exception — An AI agent encountered something it could not handle and needs human intervention.

Escalation notifications are always high priority and are delivered through all enabled channels.

In-App Notification Center

The in-app notification center is accessed by clicking the bell icon in the top navigation bar. It shows:

• A badge count of unread notifications.
• A notification list with the most recent events, showing what happened, when, and a link to the relevant item.
• Mark as read controls to clear notifications you have reviewed.
• A View All link to see your complete notification history.

Notifications appear in real time. When someone assigns you a task or comments on your request, you will see the notification appear without needing to refresh the page.

Email Notifications

Email notifications are sent to your account email address. Each email includes:

• A clear subject line describing the event (for example, "Task assigned: Configure VPN access").
• A summary of what happened and any relevant context.
• A direct link to the request, task, or workflow in Nembl so you can take action with one click.

Emails are sent individually for high-priority events and can be batched into digests for lower-priority activity, depending on your schedule settings.

Managing Notification Volume

As you use Nembl more, the number of notifications can grow. Here are strategies to keep things manageable:

• Use in-app for awareness, email for action. Keep in-app notifications broad so you have full visibility when you are in the platform. Limit email to events that require you to act.
• Set priority filters. Only receive email for High and Urgent events. See Notification Preferences.
• Use schedule windows. Batch non-urgent emails into a morning digest instead of receiving them throughout the day and evening.
• Unfollow requests you no longer need to track. If a request has moved past your involvement, unfollow it to stop receiving updates.
• Keep escalations on. Even if you reduce other notifications, keep escalation alerts active so critical issues reach you.

Notification History

All notifications are stored in your notification history, accessible from the notification center. You can:

• Search past notifications by keyword.
• Filter by type (request, task, workflow, escalation).
• Filter by date range.
• Click any notification to go directly to the related item.

This history is useful for reviewing what happened while you were away or finding a specific notification you need to act on.