Overview
Use approval requests, reviewer steps, editorial comments and content versions to govern changes before publication.
Prerequisites
- Content and approval permissions
- A configured approval workflow
Permissions required
Steps (6)
-
1
Create or edit a draft content item
Create or edit a draft content item.
Tips
Validation
Success criteria
-
2
Submit the content to the configured approval workflow
Submit the content to the configured approval workflow.
Tips
Validation
Success criteria
-
3
Open Approvals and inspect the current reviewer step and content context
Open Approvals and inspect the current reviewer step and content context.
Tips
Validation
Success criteria
-
4
Add editorial comments or request changes when revisions are needed
Add editorial comments or request changes when revisions are needed.
Tips
Validation
Success criteria
-
5
Approve the ordered workflow steps and review recorded content versions
Approve the ordered workflow steps and review recorded content versions.
Tips
Validation
Success criteria
-
6
Publish the approved content and retain the version/approval history
Publish the approved content and retain the version/approval history.
Tips
Validation
Success criteria
- The content record, approval trail, comments and versions remain linked for later inspection.
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.