How notifications work
HCM Cafe sends emails when things happen, such as a leave request waiting for approval or a payslip being published. Notifications has a tab for each part:
| Tab | What it controls |
|---|---|
| Definitions | Which events send an email, to whom, and under what conditions. |
| Templates | The subject and body of each email. |
| Data tags | The placeholders templates can use, such as the employee's name. |
| Scheduled reminders | Regular reminder emails, such as days still to be regularized. |
| Email logs | Every email sent, with delivery status. |
| Providers | The mail server emails are sent from. |
| Audit | Changes to notification settings. |
How an email is produced
- Something happens, for example a request is submitted. This is the event type.
- Each active definition for that event checks its condition rules. If they match, its recipient rules decide who gets the email: a fixed address, a data tag (such as the approver's email), a role, or a built-in resolver.
- The definition's template is filled in with data tags for each recipient.
- The email is sent through the active provider and recorded in Email logs.