Overview
Assign content to canonical placements and use placement/feed capabilities to serve authorized customer experiences with interaction state.
Prerequisites
- Content management permission
- A customer-facing application granted the required placement/feed operations
- Audience snapshot ready when the placement uses audience visibility
Permissions required
Steps (6)
-
1
Create or edit content and open its placement editor
Create or edit content and open its placement editor.
Tips
Validation
Success criteria
-
2
Select one or more canonical placement definitions and placement timing/priority settings
Select one or more canonical placement definitions and placement timing/priority settings.
Tips
Validation
Success criteria
-
3
Configure content visibility and audience requirements
Configure content visibility and audience requirements.
Tips
Validation
Success criteria
-
4
Publish the content so the feed index can materialize active placement state
Publish the content so the feed index can materialize active placement state.
Tips
Validation
Success criteria
-
5
From the customer-facing application, call placements
From the customer-facing application, call placements.feed or placements.item with trusted context.
Tips
Validation
Success criteria
-
6
Record read, dismiss, acknowledgement or other supported feed interactions
Record read, dismiss, acknowledgement or other supported feed interactions.
Tips
Validation
Success criteria
- Eligible viewers receive the content through configured placements and their feed interaction state is tracked.
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.