---
title: "Notifications and Digest"
url: "https://docs.4hse.com/guides/configurations/notifications-and-digest"
description: "Guide to configuring and managing notifications and digest summaries in 4HSE: how to set notification preferences, recipients, timing, and automatic activity overviews."
---

# Notifications and Digest

In 4HSE, **notifications** and **digests** play complementary roles in keeping users informed about tasks and deadlines.

**Notifications** are real-time alerts triggered by specific events, such as upcoming deadlines or status changes.

**Digests**, on the other hand, are periodic email summaries—sent daily, weekly, or monthly—that collect all upcoming or overdue and new activities, providing a comprehensive overview for better planning and strategy.

This guide explains how to configure both communication methods to fit individual and project needs, optimizing information flow and coordination.

## Notification Settings

[Section titled “Notification Settings”](#notification-settings)

Within the platform, **notifications** can be managed flexibly by defining:

-   **Notification preferences** at the project and office level, for the following areas: PPE, training, appointments, maintenance, procedures, and health surveillance;
-   **Who should receive the notifications** (specific recipients);
-   The **time interval** for notification delivery.

### Notification Overview

[Section titled “Notification Overview”](#notification-overview)

**Sending**:

-   Notifications are triggered automatically when a **user is assigned a role in an action** (Recipient, Assignee, Observer, Manager).

**Receiving**:

-   Occurs according to **default parameters**, visible under: _Administration → Configuration → Notifications_;
-   No customization is required to enable notification delivery;
-   Users can customize how they receive notifications via **notification preferences** (Administration → Configuration → Notifications).

**Customization**:

-   Customization is **optional**;
-   It is a **project-specific setting**, meaning each project can define its own rules;
-   It only affects **how notifications are received** (not the sending mechanism).

### How to Enable Notifications

[Section titled “How to Enable Notifications”](#how-to-enable-notifications)

1.  **Add the user profile** under the _People_ menu of a project (e.g., John Doe).
2.  **Assign the user a project permission and a non-”na” role** in the _Permissions_ menu. _(e.g., Figure 1: John Doe as project admin.)_ ![Figure 1: Assigning user role](/_astro/notifications-and-digest-1.iDF66kgo_Z1SpepF.webp)
3.  **Associate the user or an HSE role with specific actions** as Manager, Observer, or Assignee. All registered users are considered Recipients. (e.g., John Doe as Manager and Observer for all Maintenance actions in the project). ![Figure 2: Role assigned to user](/_astro/notifications-and-digest-2.D__12Wqk_ZLmbhu.webp)

You can also assign roles to **specific actions**:

For example, user Emily Carter is the Manager only for the “Emergency Plans” procedure action at the Los Angeles office. After adding him to the project, the role is assigned in the _Action details_ area. ![Figure 3: Specific roles per action](/_astro/notifications-and-digest-3.BDB_GhJt_26rrVD.webp)

### Notification Preferences

[Section titled “Notification Preferences”](#notification-preferences)

Notifications are received based on:

-   **Section**: The action or management context (e.g., Training, Appointments);
-   **Event**: Based on the expiration date of the latest valid record or the date of the upcoming scheduled event;
-   **Role**: The user’s role in the action (Manager, Observer, Assignee, Recipient). All registered users are considered Recipients;
-   **Interval**: The time range used for calculation;
-   **New**: includes registrations with status “New” in the notification, treating them as activities to be regularized (option available only when the “Expiration” event is selected);
-   **When**: Option to define a lead or delay time (in days) relative to the interval.

![notification configuration](/_astro/notifications-and-digest-4.C7MbzASx_1AMEBk.webp)

## Digest Configuration

[Section titled “Digest Configuration”](#digest-configuration)

The digest is a periodic email summary of upcoming or overdue activities. Configuring it is a user preference: see [Digest](/guides/user-preferences/digest).

This site is protected by reCAPTCHA and the Google [Privacy Policy](https://policies.google.com/privacy) and [Terms of Service](https://policies.google.com/terms) apply.