Announcements — Viewing and Creating

By Monirul Islam · 2026-03-13 · Announcements

Announcements are the noticeboard: one message written once and shown to everyone who should see it. This guide covers reading them, writing them if you are Admin or HR, and the three settings that decide who sees what and for how long.

Open Announcements from the sidebar — everyone has it. You see the ones targeted at your role that have not expired; nothing else appears, so a short list does not mean nothing was posted.

Recent announcements also surface on your dashboard, so the everyday case needs no navigation at all.

Admin and HR only. Managers can read announcements but not create them — company-wide messaging is deliberately narrow, because an announcement reaches people who cannot opt out of it.

1. Open Announcements and create a new one.
2. Write the title and content.
3. Set the priority.
4. Choose the target roles.
5. Optionally set an expiry date.
6. Publish.

Everyone targeted is notified, subject to your organization's notification settings — if the Announcements category is disabled, the message still appears on the noticeboard but generates no notification. See notification settings.

Two priorities. Normal is everything. Urgent is displayed more prominently and should be rare.

Urgent works exactly as long as it is unusual. An office closure, a systems outage, a safety issue — those are urgent. A policy reminder, a social event, a form deadline next month are not, and marking them so trains people to ignore the styling that was supposed to make them look up.

You can target Admin, HR, Manager, Team Lead, Management and Employee in any combination.

Targeting is not about secrecy — it is about relevance. A message about approving leave before month end matters to managers and is noise to everyone else, and noise is what makes people stop reading the board. Send to everyone when it genuinely concerns everyone; otherwise narrow it.

Note the practical trap: if you target only managers, employees will never see it, and someone will eventually say "nobody told us". Where a message affects everyone but requires action from some, one announcement to all with the action named in it usually beats two announcements.

An expiry date removes the announcement from the board automatically on that day. It is optional, and leaving it blank means the announcement stays until somebody deletes it.

Set one for anything time-bound — an event, a deadline, a temporary arrangement — at the moment you write it. A noticeboard that still shows last quarter's fire drill is one nobody reads, and cleaning it up later is a job that never gets prioritised.

Leave it blank only for genuinely standing information.

Admin and HR can edit or delete any announcement.

Editing changes the message in place; people who already read it will not be told it changed. For a correction that matters — a wrong date, a wrong location — post a new announcement rather than quietly editing the old one, because the people who most need the correction are the ones who already read it and will not look again.

Deleting removes it entirely. If a message has simply run its course, letting it expire is tidier than deleting, and setting an expiry when you write it removes the decision altogether.

• Put the point in the title. "Office closed Monday 3 March" beats "Important notice". Many people read only titles.
• Say what the reader must do, and by when. An announcement with no action should say so, so nobody hunts for one.
• One subject per announcement. Two topics in one message means the second is missed.
• Post fewer of them. Frequency is the main thing that kills a noticeboard. If everything is announced, nothing is.

Check the target roles first — this is the usual cause. Then check whether it had already expired when they looked, and whether your organization has announcement notifications enabled; without them the message appears on the board but arrives silently.

No. Announcements publish when you create them; expiry controls when they disappear, not when they appear.

No read receipts. For anything requiring confirmed acknowledgement, an announcement is the wrong tool — pair it with something that produces a record.

No. Announcements are organization-wide and role-targeted, not team-targeted, and only Admin and HR can create them.

• Notification settings — whether announcements also notify
• Understanding your dashboard — where recent announcements appear
• Roles and permissions — the roles you can target