Announcements & the login message
Two ways to reach everybody, and when to use each.
Noots gives you two broadcast channels, and they're for different urgencies.
| Announcements | Login message | |
|---|---|---|
| Where it appears | A notification for everybody, the Announcements page, and — if you pin it — the top of everyone's home screen. | A modal, once, the next time somebody signs in. |
| Best for | A policy change, a launch, something people should be able to go back and read. | Something they must see before carrying on — a maintenance window, an urgent change. |
| Audience | Everyone in the workspace. | The whole organization, or a single team. |
| Where to write it | Organization → Announcements. | Org settings → Login Message. |
The three settings on an announcement
| Setting | What it does |
|---|---|
| Pin to the home screen | The post sits at the top of everybody's home until you unpin it — on both home layouts, the command centre and the classic view. |
| Require acknowledgement | Everybody is asked to confirm they've read it. Until they do, it stays on their home screen and on a bar across every page. It never blocks the app. |
| Also email everyone | One email to every verified member, sent once. Safe to leave off — the notification and the home screen already reach people in the product. |
Seeing who has read it
Open an announcement you posted and click the read count underneath it. You get the people who haven't acknowledged it by name, the people who have with the time they did, and a button to remind only the ones still outstanding.
Posting, pinning and deleting need the member-management permission — owners, admins and managers. Reading and acknowledging are open to everybody, because an acknowledgement is the member's half of the deal.
A team-only login message needs only the member-management permission, so a supervisor can message their own team without being a workspace admin. An org-wide one needs organization edit rights.