Notifications

The Notifications module allows defining which system actions trigger notifications and to which users, HCPs or HCP types they are sent. The route is /manage-notifications/notifications.

Key concepts

• Action (NotificationAction): each system action that can trigger a notification.
• Scope (NotificationScope): recipient configuration for an action. Defines to which users, HCPs or HCP types it is sent.
• Scope status: active or inactive.
• Exclude actor: if active, excludes the user who performed the action from the recipient list.

How the screen is organized

The main screen loads the system actions and the configured scopes. Above the list there is a free search engine that filters by label, description or module.

Each action may have a configured scope. When clicking on the action you can:

• See the current scope status.
• See the recipient users.
• See the recipient HCPs.
• See the recipient HCP types.
• Save the scope configuration.

Available actions

• Configure scope: select recipient users, HCPs or HCP types.
• Activate or deactivate scope: enable or disable the sending of notifications for the action.
• Mark "exclude actor": prevent the user who performed the action from receiving the notification.

Roles and permissions

Access to the module is controlled by the associated submodule's permission. The notifications themselves do not require a special permission beyond the module's read access.

Documented features

Feature	Page
Configure notification recipients	Configure notification recipients
Activate or deactivate notification sending	Activate or deactivate notification sending
Exclude actor from notification	Exclude actor from notification

Relation with other modules

• System actions: notifications are linked to the actions managed by the Staff types and actions module.
• Audit log: scope configuration and changes are recorded.
• Users and HCPs: the recipients come from these catalogs.

Operational recommendations

• Activate only the necessary notifications to avoid saturating the team.
• For sensitive actions (for example, reschedule), include the coordinator or administrator.
• Use "exclude actor" when the notification is for other users to review the action.
• Document internally the recipient convention.