Overview
Create an announcement with visibility, placement, acknowledgement and timing controls, then move it through the configured publishing workflow.
Prerequisites
- Content management permission
- A configured workflow for the announcement type when approval is required
Permissions required
Steps (4)
-
1
Open Announcements and create a new announcement
Open Announcements and create a new announcement.
Tips
Validation
Success criteria
-
2
Set the announcement details, priority, visibility, placements and acknowledgement behavior
Set the announcement details, priority, visibility, placements and acknowledgement behavior.
Tips
- Use placement and visibility controls to determine where eligible viewers receive the announcement.
Validation
Success criteria
-
3
Submit, review and approve the announcement according to the configured workflow
Submit, review and approve the announcement according to the configured workflow.
Tips
Validation
Success criteria
-
4
Publish immediately or schedule publication and expiry
Publish immediately or schedule publication and expiry.
Tips
Validation
Success criteria
- The announcement is available through authorized announcement and placement/feed operations during its active publication window.
About this guide
EngagementHub gives workspace teams one governed system for news, announcements, events, promotions and coordinated campaigns. Content shares a common publishing model for titles, summaries, bodies, categories, tags, calls to action, media references, attachments, visibility, placements, related records, versions and publication state.
Editorial work moves through configurable review and approval steps before immediate or scheduled publication. The publication engine maintains schedules, expiry, feed indexing and per-viewer feed state. Events add occurrences, registration windows, capacity, waitlists, attendance, reminders and feedback. Promotions add codes, claims and claim lifecycle records. Campaigns add goals, channels, assets, stages, runs and measurable outcomes.
Audience targeting is provider-driven. EngagementHub discovers applications that advertise the audience-provider contract, loads catalogues and categories, establishes least-privilege provider access, and freezes returned members into reproducible snapshots. Secure media is delegated to the configured file-storage provider, while queued communication requests are handed to the configured notification-routing provider.
For application interoperability, EngagementHub exposes a canonical capability runtime across Handler, RCP and Bridge v2, implements the eight-operation ContextResolver contract, publishes domain events through the platform EventBus, consumes trusted project-reference and email-delivery events, and supports signed outbound webhooks with retries and delivery logs.