Overview
Connect a secure-file provider, upload or select files, bind them to EngagementHub content, and issue customer-safe delivery tokens.
Prerequisites
- Media/files management permission
- Compatible secure-file provider connected
Permissions required
Steps (6)
-
1
Open Integrations and confirm Secure file storage & delivery is configured
Open Integrations and confirm Secure file storage & delivery is configured.
Tips
Validation
Success criteria
-
2
Open Media & placements or a content editor and browse provider files
Open Media & placements or a content editor and browse provider files.
Tips
Validation
Success criteria
-
3
Upload a new file through EngagementHub secure ingress when required
Upload a new file through EngagementHub secure ingress when required.
Tips
Validation
Success criteria
-
4
Bind the selected file to content as cover media, media or attachment
Bind the selected file to content as cover media, media or attachment.
Tips
Validation
Success criteria
-
5
Publish the content to an authorized placement
Publish the content to an authorized placement.
Tips
Validation
Success criteria
-
6
Request the content file through the delivery capability
Request the content file through the delivery capability.
Tips
Validation
Success criteria
- EngagementHub authorizes the content request and obtains a provider delivery token for the file reference.
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.