Overview
Use schedule records and lifecycle workers to coordinate scheduled publication, expiry and related engagement actions.
Problem
Publishing teams need a durable source of timed engagement actions.
Solution
EngagementHub stores publication schedules and exposes them through the Studio calendar while workers process due actions.
How it works
Publishers create schedule records for supported entities and actions, review them on the calendar, and allow background workers to execute due publication and lifecycle work.
Who is this for
Expected outcomes
- Durable schedule records
- Calendar visibility across engagement activity
- Background processing of due actions
Key metrics
Scheduled actions with stored execution time
0 %
100 %
Due schedule actions reconciled by workers
0 %
100 %
Calendar items linked to source entities
0 %
100 %
Gallery
Security impact
- Publication schedules, calendar projections, entity status and execution timestamps · PII: Workspace actor identifiers can appear in schedule audit metadata
Compliance
- Workspace-scoped application permissions and trusted execution context
- Operation/resource authorization for application calls
- Auditable workflow, queue, event or interaction records for this use case