Overview
Prepare the Studio, permissions, outbound providers, inbound application access, placements and webhook settings used by your workspace.
Prerequisites
- EngagementHub installed in the target workspace
- Workspace roles and EngagementHub permissions assigned
- Any required provider applications installed and advertising their capabilities
Permissions required
Steps (6)
-
1
Open EngagementHub and confirm the Studio dashboard loads
Open EngagementHub and confirm the Studio dashboard loads.
Tips
Validation
- The Studio shell shows Home, Content, Announcements, Events, Promotions, Campaigns, Audiences, Calendar, Approvals, Media and Analytics.
Success criteria
-
2
Review Settings and the mandatory placement catalogue
Review Settings and the mandatory placement catalogue.
Tips
- Workspace-specific settings and templates can be added after the application is installed.
Validation
- The canonical placement definitions are available.
Success criteria
-
3
Open Integrations and discover installed applications
Open Integrations and discover installed applications.
Tips
Validation
Success criteria
-
4
Connect the notification-routing and secure-file provider roles required by your workflow
Connect the notification-routing and secure-file provider roles required by your workflow.
Tips
Validation
Success criteria
- Required outbound provider roles show as configured.
-
5
Review inbound application grants, Bridge clients and webhook endpoints as needed
Review inbound application grants, Bridge clients and webhook endpoints as needed.
Tips
Validation
- Only intended callers, scopes and endpoints are active.
Success criteria
-
6
Return to Studio and create a draft content item to confirm the workspace is ready
Return to Studio and create a draft content item to confirm the workspace is ready.
Tips
Validation
Success criteria
- The draft is saved and available in Content.
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.