Announcements

Announcements are notice-board posts for your team or workspace. They can go live immediately or at a future time, remain pinned, and expire when the information is no longer relevant. Unlike memos, announcements have no approval step.

Access needed

Access depends on your assigned permissions and workflow scope.

Read visible announcements and mark your own seen status: notices.read
Audience, publication time, expiry and archive status constrain visibility.
Role and permission labels
Typical responsibility: Authorized announcement reader or poster. Role names alone do not grant access.
Read announcements and record own seen status
Post or manage your own team announcements: notices.post.team
Alternatively notices.post.all is accepted. Direct-report audience requires a linked employee. Viewing the board separately requires notices.read.
Role and permission labels
Typical responsibility: Authorized announcement reader or poster. Role names alone do not grant access.
Post team announcements
Post workspace-wide or manage other authors’ announcements: notices.post.all
Workspace-wide posting does not additionally require notices.post.team. Board reads separately need notices.read.
Role and permission labels
Typical responsibility: Authorized announcement reader or poster. Role names alone do not grant access.
Post and manage workspace announcements
View who marked your announcement seen: notices.post.team
The author needs a posting grant; notices.post.all is an alternative and can inspect other authors’ posts. Only recorded seen actions appear.
Role and permission labels
Typical responsibility: Authorized announcement reader or poster. Role names alone do not grant access.
Post team announcements

Demo screenshots may show broader access than your account.

Read the notice board

Open Notifications → Announcements. Review the title, category, audience, poster, publication time and your reading status. Pinned posts appear first. Use filters and sorting to find relevant news, or Refresh announcements to reload the board.

Populated announcement board with fictional welcome post — Fictional demo announcement; controls depend on your permissions and ownership.

Select Read announcement to open the message. Check its audience and publication time, read its content, then use Mark as seen when appropriate. Opening a message and recording that you have seen it are separate actions.

Fictional welcome announcement reader with Mark as seen and author controls — Fictional demo announcement; controls depend on your permissions and ownership.

Copy link lets you refer to a visible post. The recipient still needs access to its audience and the announcement must remain available; a link does not broaden access.

Publish an announcement

Write a clear message
Select New announcement. Enter a Title of up to 200 characters and the announcement content. Use the formatting toolbar where helpful and review the finished text as a reader would see it.
Choose audience and category
Select the intended audience and a category that helps readers find the update. Entire workspace requires workspace-wide posting access. Team posting depends on your linked employee and direct-report relationships.
Set publication and expiry
Leave Publish date empty to publish now, or choose a future date and time. Times use your local timezone. An optional expiry must be later than publication. Pin only when the message needs to stay above ordinary posts.
Review notification scope
Check Notify recipients when published. When enabled, notifications are requested when the announcement goes live, subject to recipient preferences and available delivery channels. Turning it off does not hide the board post.
Publish and verify
Review the publication summary and select Publish announcement. Check the saved result. Once publication time is reached, refresh the board and open the post to verify its content and audience.

Demo announcement composer with recipient notifications off — Fictional demo announcement; controls depend on your permissions and ownership.

The demo welcome announcement is fictional, published to the workspace with recipient notifications disabled. Its purpose is to illustrate the board and reader view, not to prescribe your organization's announcement content.

Edit and pin existing posts

Open a manageable post and use Edit to review its title, content, audience, category, dates and pinned state. Save and reopen it to verify the result. Pin or the row's pin action changes its placement on the board; it does not change who can read it.

The author can manage their own post within their posting scope; workspace-wide posting access can manage other authors' posts too. The original recipient-notification choice cannot be changed through editing. Do not assume an edit sends another notification.

Review viewers

Use Viewers where available to inspect who has explicitly marked the announcement seen and when. This is available to the poster with posting permission or someone with workspace-wide posting access. An empty viewers list does not prove nobody opened or read the message; seen status requires the recording action.

Expiry and archiving

After its expiry, a post is no longer visible through the ordinary reader view. Archive removes a published announcement from visibility and makes it no longer editable. Review the post and audience before confirming an archive action. Archiving a post does not recall a notification already delivered.

Troubleshooting

Problem	What to check
A post is missing	Check audience, publication time, expiry, archive status and filters.
Entire workspace is unavailable	It requires notices.post.all. Team posting is a different scope.
Team posting fails	Check your linked employee and direct-report relationships.
A scheduled post does not open yet	Ordinary reading starts when its publication time is reached.
A published post produced no inbox item	Check its notification choice, recipient eligibility and personal preferences.
Edit, Archive or Viewers is unavailable	Check posting permission, ownership and current visibility.
Seen status differs from inbox Read	They are separate records and actions.

What was verified

A fictional workspace announcement was created with notifications off and verified on the board and in its reader view after publication. Three light-theme screenshots cover composition, list and detail. No seen action, pin, edit, archive or viewer report was executed. Restricted employee access and scheduled/expiry behavior were not tested.