Sarah publishes company notices and important updates through the platform so employees always receive clear and organized communication.
From policy announcements to urgent alerts, employees stay informed through dashboard notices and notifications delivered to the right audience at the right time.
Company announcements and notifications are published successfully, allowing employees to receive timely updates through dashboard alerts and configured delivery channels.
Publishing is the trigger, and it fires once. The audience scope does double duty: it decides who can read the notice and who gets told about it, so the two can never drift apart — All reaches everyone in the company, Employee reaches company members holding no role beyond Employee, and Admin reaches everyone holding another company role. The alert lands in the bell menu and is pushed live to anyone already signed in. The admin who published it is left out, because they already know.
Priority decides whether the alert also leaves the app. LOW and NORMAL stay in-app; HIGH and CRITICAL are emailed to the same audience on top of the in-app alert. That split exists so routine announcements do not train people to ignore the sender.
| Failure | What the user sees | What happens next |
|---|---|---|
| Notice expiry date is earlier than publish date | Validation rejects notice configuration | Select a valid publish and expiry date range |
| Notice reaches its expiry date | Expired notice becomes automatically hidden | Republish or extend notice duration if needed |
| Notification or email delivery fails while publishing | The notice still publishes and is readable | Delivery is best-effort and retried by the queue; a broken mail server never blocks an announcement |
| Scenario | Behavior | Why |
|---|---|---|
| Notice published at HIGH or CRITICAL priority | Email is sent on top of the in-app alert | Priority is the only urgency signal a notice carries, so it is what decides whether the alert leaves the app |
| Employees configure notification delivery preferences | An explicit email opt-out for notices is honoured; the in-app alert still arrives | Opting out of mail is not opting out of the notice |
| A published notice is edited | No second alert is sent | A notice is announced once; publish a new notice if people need telling again |
| Notice audience matches nobody | Nothing is sent and the publish still succeeds | An empty audience is a scoping mistake, not a reason to block the notice |