Loading…
Velaxe
EngagementHub — Governed Content, Events, Promotions, Campaigns & Engagement Analytics | Velaxe

EngagementHub

Schedule publishing, expiry, registration, and campaign activity

Use the publication calendar and schedule records to coordinate timed content and campaign activity.

10 min Beginner Publishers and campaign managers Updated Jul 24, 2026
View App All Guides
Schedule publishing, expiry, registration, and campaign activity guide
Use the publication calendar and schedule records to coordinate timed content and campaign activity.

Overview

Use the publication calendar and schedule records to coordinate timed content and campaign activity.

Prerequisites

  • Calendar access
  • Content or campaign records to schedule

Permissions required

engagementhub.calendar.manage engagementhub.calendar.view engagementhub.content.manage

Steps (6)

Estimated: 10 min
  1. 1

    Open Publishing Calendar and choose the date range to review

    Publishers and campaign managers 3 min Back to top

    Open Publishing Calendar and choose the date range to review.

    Tips

    —

    Validation

    —

    Success criteria

    —

  2. 2

    Create a schedule for a supported entity and action

    Publishers and campaign managers 5 min Back to top

    Create a schedule for a supported entity and action.

    Tips

    —

    Validation

    —

    Success criteria

    —

  3. 3

    Set the scheduled time and required payload metadata

    Publishers and campaign managers 4 min Back to top

    Set the scheduled time and required payload metadata.

    Tips

    —

    Validation

    —

    Success criteria

    —

  4. 4

    Save the schedule and confirm it appears on the calendar

    Publishers and campaign managers 3 min Back to top

    Save the schedule and confirm it appears on the calendar.

    Tips

    —

    Validation

    —

    Success criteria

    —

  5. 5

    Allow the publication and lifecycle workers to process due schedules

    Publishers and campaign managers 3 min Back to top

    Allow the publication and lifecycle workers to process due schedules.

    Tips

    —

    Validation

    —

    Success criteria

    —

  6. 6

    Review the resulting entity status and schedule history

    Publishers and campaign managers 2 min Back to top

    Review the resulting entity status and schedule history.

    Tips

    —

    Validation

    —

    Success criteria

    • Timed publication/lifecycle actions are reflected in the calendar and target entity state.

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.