Internal Announcements · One-Way Internal Notices
Post a one-way internal notice to staff, targeted by role or department, with an Urgent, Normal, or Info priority: Urgent overrides notification mute.
Internal Announcements are one-way internal notices to the people in your organization. Use them to tell your staff something, a policy change, an all-hands reminder, a system outage, without opening a conversation. Internal Announcements are not for donors or external contacts; they reach your own team, and you target exactly who needs to see each one.
When to Use Internal Announcements
An announcement is the right tool when you’re informing staff and don’t need replies. If you need a reply, use Messages. If you’re reaching donors or an external audience, use a Broadcast. See Messages vs Broadcasts vs Internal Announcements for the full comparison.
| You want to… | Use |
|---|---|
| Tell the whole team about a new policy | Internal Announcements |
| Alert the Finance department to a deadline | Internal Announcements |
| Ask a teammate a question | Messages |
| Send a fundraising appeal to donors | Broadcasts |
Posting an Announcement
- Go to Communications → Internal Announcements.
- Click New Announcement.
- Choose your audience: by role or department (see Targeting).
- Set the priority: Urgent, Normal, or Info.
- Write the title and body.
- Click Post.
The announcement is delivered to everyone in the targeted audience as an in-app notification. It does not start a conversation: recipients read it but don’t reply through the announcement.
Targeting
You decide who sees each announcement:
| Target | Reaches |
|---|---|
| Everyone | All staff in your organization |
| By role | Everyone holding a specific role (e.g. all Managers) |
| By department | Everyone in a team or department (e.g. Operations) |
Targeting keeps notices relevant: a department-specific reminder doesn’t clutter everyone else’s notifications.
Priority Levels
Every announcement carries a priority that controls how prominently it’s surfaced:
| Priority | Use it for | Behavior |
|---|---|---|
| Urgent | Time-critical notices that must not be missed (outage, emergency closure) | Surfaced prominently and overrides notification mute: see below |
| Normal | Standard team notices (policy update, meeting reminder) | Delivered as a normal in-app notification |
| Info | Low-priority, good-to-know items | Delivered quietly; recipients see it in their notification list |
Urgent Overrides Mute
Recipients can mute or quiet their notifications, but an Urgent announcement is delivered anyway. This is intentional: a critical, time-sensitive notice reaches every targeted person even if they’ve silenced routine alerts. Reserve Urgent for notices that genuinely warrant breaking through: overusing it trains people to ignore it.
Recipients control their own routine notification preferences under Settings → Notifications; Urgent priority is the deliberate exception that bypasses those preferences.
Internal Announcements and Consent
Marketing consent does not apply here, and that is deliberate. An internal announcement reaches the staff of your own organization as an in-app notification about their work, a policy change, a closure, a deadline. It is not marketing, and there is no unsubscribe from it.
Three things follow:
- Internal Announcements never reach donors, members, parents or external contacts. If you need to reach an external audience, use a Broadcast, which is consent-checked and carries an unsubscribe link.
- A staff member’s own marketing preference is irrelevant to an announcement. Someone who has switched off Marketing & announcement emails on their personal record still receives internal notices.
- Posting one is a permission, not a role. Drafting, publishing and deleting announcements each sit behind their own announcement permission, separate from the one that governs broadcasts, so you can let someone post staff notices without also letting them mail your donor list.
Reading the announcements addressed to you needs nothing beyond being signed in.
When it goes wrong
| What you see | What to do |
|---|---|
| New Announcement is missing | Posting needs the announcement permission. Ask your owner or admin; broadcast access alone is not enough. |
| Nobody in a department saw the notice | Check the targeting. A role or department target reaches only people currently holding that role or sitting in that department. |
| You targeted a role and the count looked low | Roles are per person, so someone who left the role no longer receives it. Target Everyone if the notice genuinely applies to all staff. |
| You posted at Urgent and people complained | Urgent bypasses muted notifications by design. Use Normal for anything that is not time-critical. |
| You want to reach donors or parents | Internal Announcements cannot. Use a Broadcast or a Message instead. |
| You need to withdraw a notice | Delete it. It stops appearing, but anyone who has already read it has already seen it, post a correction if the content was wrong. |
Next Steps
- Messages vs Broadcasts vs Internal Announcements: choose the right communication tool
- Messages: start a two-way conversation instead
- Notification Settings: how recipients manage their alerts
- Communications Hub overview: the full module