Overview
Consume Project Board project updates and maintain source-owned project references for related EngagementHub content.
Problem
Engagement content may need project context while project ownership remains in the project application.
Solution
EngagementHub consumes trusted Project Board events and stores project references in its remote entity cache.
How it works
Project updates arrive through EventBus, EngagementHub validates the managed event envelope, updates or invalidates the project reference, and content can retain the project identifier for relationships, filtering and context resolution.
Who is this for
Expected outcomes
- Source project identity preserved
- Project update and delete events processed durably
- Context relationships can point to source-owned project references
Key metrics
Project reference events stored in Event Inbox
0 %
100 %
Cached project references retain source app/entity identity
0 %
100 %
Delete events mark cached project references invalidated
0 %
100 %
Gallery
Security impact
- Project reference cache, source application/entity identity, event inbox state and linked content references · PII: Project metadata may include names/status supplied in the trusted event payload
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