Notification Definitions

The Notification Definitions module allows organizations to define specific notification contexts and assign recipients dynamically.
It enables flexibility and easy updates for automated processes like email notifications.

Main Table: notification_definitions

Purpose: Defines notification contexts and stores recipient information for each context.

• `name`: Descriptive key for the notification context (e.g., staff_onboarding).
• `staff_json`: A hidden field automatically populated with the IDs of employees when they are added as recipients.

Example:

• `staff_onboarding`: Used for sending emails during the onboarding step for staff. Recipients are dynamically managed in staff_json.

Submodule: notification_definitions_recipients

Purpose: Allows users to assign employees to specific notification contexts.

Example Workflow:

1. Select the notification context (e.g., staff_onboarding).
2. Add or update the list of employees who should receive notifications for that context.
3. Notifications will automatically be sent to the updated list of recipients when the context is triggered.

Benefits

• Flexibility: Easily update recipients as organizational needs change.
• Centralized Management: Keep all notification settings and recipients organized.
• Dynamic Updates: Ensure real-time accuracy for recipient lists.

For instance, if new employees need to be added as recipients for the onboarding process (such as IT or HR staff, depending on the organization's structure), you can easily update the recipient list for staff_onboarding without altering the system's core logic.