> For the complete documentation index, see [llms.txt](https://docs.labii.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.labii.com/widgets/section-widgets/productivity/communication/notifications.md).

# Notifications

## Specs

| Label                     | Value                         |
| ------------------------- | ----------------------------- |
| **Version**               | 0.3.0 (updated on 2024-07-29) |
| **Developer**             | Labii Inc.                    |
| **Type**                  | Section                       |
| **Support Configuration** | No                            |

## Overview

The Notifications widget provides efficient management and distribution of email-based notifications directly from a record. It serves as an upgraded replacement for the legacy Emails widget, offering a structured inbox and sent history so team members can both send and track communications without leaving the record context. Users can notify leads, customers, or colleagues with record-linked messages, and the two-tab interface keeps incoming and outgoing correspondence clearly separated. This widget is essential for any workflow that requires auditable, record-associated communication.

## Use Cases

* **Customer Outreach**: Send scheduled or ad-hoc notifications to customers or leads directly from a CRM or sales record, keeping all correspondence tied to the relevant entry.
* **Team Updates**: Notify team members of status changes, task assignments, or decisions made on a project or experiment record.
* **Process Communication**: Trigger notifications at specific process steps (e.g., approval requests, handoff alerts) so the right people are informed at the right time.
* **Inbox Monitoring**: Use the inbox tab to track incoming replies or acknowledgments linked to the record, providing a complete communication thread in one place.
* **Sent History Audit**: Review the sent tab to confirm which notifications were dispatched, by whom, and when — supporting accountability and audit requirements.

## Configuration

The Notifications widget requires no configuration. It is ready to use immediately after being added to a record — no setup or adjustment is needed.

{% hint style="info" %}
Because the widget has no configuration, the same inbox/sent interface is available on every record in the table automatically.
{% endhint %}

## Interface

### Read-only View

The widget presents two tabs: **Inbox** and **Sent**. Each tab displays a list of notifications with the sender or recipient identity, notification name, and date. Clicking a notification name opens its full content.

<figure><img src="/files/JhCNDqUMCXXsm73iOl6b" alt="Read-only view of the Notifications widget showing the Inbox and Sent tabs"><figcaption><p>The Notifications widget displays incoming and outgoing notifications in separate tabs for organized communication tracking</p></figcaption></figure>

## Additional Functions

### Add Notification

{% stepper %}
{% step %}
Click the **+ Notification** button in the widget header.
{% endstep %}

{% step %}
Fill in the notification fields. By default, the notification is pre-associated with the current record. For a full description of available fields, refer to the [Notifications](/user-guide/side-menu/notifications.md) user guide.
{% endstep %}

{% step %}
Submit the notification. It will appear in the **Sent** tab and be delivered to the specified recipients.
{% endstep %}
{% endstepper %}

### Inbox

The **Inbox** tab lists all notifications received in relation to this record. Each entry displays:

* **Sender** — Who sent the notification
* **Name** — The notification title (click to view full content)
* **Date** — When it was received

### Sent

The **Sent** tab lists all notifications dispatched from this record. Each entry displays the recipient, notification name, and send date, providing a clear history of outbound communications.

### Delete Notification

Click the **Delete** icon next to any notification to permanently remove it from the system.

{% hint style="warning" %}
Notification deletion is permanent. Once deleted, the record of that communication is lost — confirm before deleting notifications that may be needed for audit or compliance purposes.
{% endhint %}

## Best Practices

### Communication Organization

* Use the **Sent** tab to confirm delivery before following up with recipients, avoiding duplicate messages.
* Include a descriptive notification name so recipients and team members can identify the message purpose at a glance from the list view.

### Workflow Integration

* Add the Notifications widget to process or approval records where stakeholder communication is a required step.
* Pair with the [Comments](/widgets/section-widgets/productivity/communication/comments.md) widget to keep formal notifications separate from informal discussion on the same record.

### Audit and Compliance

* Review the **Sent** tab periodically to verify that required communications were sent at the correct workflow stages.
* Avoid deleting sent notifications when they serve as evidence of communication in regulated or audited workflows.

### Common Pitfalls to Avoid

* **Avoid** sending notifications without associating them to the correct record, as this breaks the audit trail linking communication to data.
* **Avoid** using this widget as the sole communication log for FDA-regulated submissions — supplement with compliant documentation widgets.