News Feed
Company feed for announcements, updates, and discussions with Must-Read acknowledgement tracking.
MangoApps
Overview
News Feed is a unified company feed with a clear content hierarchy — Must-Read, Operational, and Social — designed for frontline and corporate workforces alike. Most company feeds collapse policy updates, operational reminders, shout-outs, and water-cooler chat into a single noisy timeline; News Feed separates them by design so the things employees must see are never buried under the things they merely enjoy seeing. Must-Read posts require an explicit acknowledgement, expire on a configurable window, and automatically demote to Operational when the window closes — acknowledgements are immutable and reportable for compliance audits. Authors compose Updates, Questions, or quick Polls; questions become a Q&A surface where authors and admins mark a Correct Answer that feeds a knowledge base for search and AI auto-answer suggestions. Audience targeting scopes posts to everyone or to segments and virtual groups like direct reports, with per-segment notification frequency controls (realtime, hourly, daily) so frontline managers do not get the same firehose leadership does. Role-gated Signals, SMEs, and Analytics surfaces sit alongside the feed for managers and admins to act on engagement, identify subject-matter experts from real participation, and measure read-through, acknowledgement rates, and sentiment over time. Roughly fifty admin toggles — covering composer types, AI features, reactions palette, signal thresholds, SME scoring weights, voice and video, must-read permissions, and notification defaults — make News Feed a governed communications channel rather than a chronological wall.
Highlights
Capabilities
Content Hierarchy
-
Operational vs Social content split with configurable labels
-
Must-Read posts with persistent Acknowledge CTA
-
Must-Read expiry with automatic fall-back to Operational
-
Per-business content-category labels
Composer
-
Update composer with priority pills, audience, and expiry
-
Question composer
-
Poll composer (single-select, 2–5 options)
-
Ranked-choice polls Ships with the poll results release (PRD 05).
-
Draft auto-save (one draft per user)
-
Scheduled publishing
-
Automatic expiry and archival
-
15-minute post-publish edit window
-
Draft, scheduled, published, expired, archived lifecycle
Audience & Permissions
-
Everyone vs segment-targeted audiences
-
Role-gated Signals, SMEs, Analytics, and Settings tabs
-
Configurable "Who can post to Everyone" policy
-
Configurable "Who can mark Must-Read" policy
Engagement
-
Idempotent read tracking via in-viewport dwell
-
Immutable acknowledgement records
-
Per-post mute / unmute
-
Reactions and comments Reactions and comments ship in a follow-up release.
Notifications
-
Per-user, per-segment notification frequencies
-
Must-Read notifications always real-time
AI Features
-
AI settings persisted (authoring, topic assignment, summarization, routing) Behaviour ships in follow-up AI releases.
-
News Feed AI Agent Agent ships in a future release.
Use cases
Resources
FAQ
Must-Read is an escalated Operational post that requires a persistent Acknowledge from recipients and has a mandatory expiry date. After expiry, Must-Read posts automatically appear as standard Operational posts.
No. Must-Read is reserved for Operational content so that social content cannot be used to force acknowledgement.
Posts are either sent to Everyone in the business or scoped to one or more segments. Segment resolution supports groups and virtual segments like "My Direct Reports".
The post still appears in their feed if they navigate to it, but the user no longer receives notifications for comments, reactions, or reminders.
Read is recorded when a feed card remains in the viewport for a short dwell period. Read records are idempotent per (user, post).
Signals and SMEs are visible to managers, leadership, and admins. Analytics is additionally visible to leadership. Settings is admin-only.