News Posts

What news posts are

News posts are team-scoped announcements in Navis Docs. Admins use them to share updates, operational changes, reminders, and context that the whole team should see.

Each team has its own news area, so announcements stay close to the procedures and working knowledge they relate to. Posts are stored as rich text using TipTap JSON, which keeps formatting structured and consistent.

When to use news

Use news posts for information that should be visible to a team but does not need to become a procedure itself.

• Announcing a change to how the team works
• Sharing a reminder about an upcoming operational deadline
• Highlighting a newly published or updated procedure
• Giving context around a policy, training, or compliance update

If the update includes step-by-step instructions that members should use repeatedly, create or update a procedure as the source of truth and use a news post to announce the change.

Pinned posts

Admins can pin important posts so they stay prominent for the team. Pinning is useful for announcements that should remain easy to find, such as launch notices, temporary process changes, or time-sensitive guidance.

Keep pinned posts current. Once an announcement no longer needs special attention, unpin it so newer high-priority updates can take its place.

Read receipts and unread counts

Navis Docs tracks when each member has seen a news post. That read receipt is recorded as a UserNewsRead, which links the user to the post they have read.

Members see an unread count in the sidebar, making it easy to notice new announcements. Opening and reading the post clears it from that member's unread count.

How news connects to procedures

Procedure publishing can create a related news post automatically. When an admin enables newsOnPublish, Navis Docs creates a team news post as part of the publish workflow.

This is useful when a procedure change should be both available in the knowledge base and announced to the team. For larger changes that need acknowledgment, combine news with a rollout. See Procedure Rollouts for more detail.

Permissions

News creation and deletion are admin-only actions. Admins and owners can create posts, pin announcements, remove posts when needed, and decide whether publishing a procedure should also create a news post.

Members read team news and mark posts as read. This keeps everyday news consumption simple while preserving admin control over official team announcements.

Suggested news workflow

1. Choose the right team

Create the post in the team that owns the announcement. If an update applies to multiple teams, write separate posts so each team receives the right context.

2. Write the announcement

Keep the post focused on what changed, who it affects, and what members should do next. Link to the relevant procedure when the announcement depends on detailed instructions.

3. Pin only when needed

Pin the post if it should remain highly visible. For routine updates, leave it unpinned so the news feed stays chronological.

4. Review read progress

Use unread counts and read receipts to understand whether the team has seen the announcement. For updates that require formal acknowledgment, publish a procedure rollout instead of relying on news alone.