Overview
Resolve messages, threads, drafts, templates, campaigns, attachments and related Email Hub entities through ContextResolver without duplicating source data.
Problem
Other workspace applications need current email context and safe actions while Email Hub remains authoritative for its own mailbox and campaign records.
Solution
Use Email Hub context capabilities for entity projections, relationships, timeline, presentation, permissions, actions and change subscriptions.
How it works
Trusted consumers resolve EntityRefs and can discover authorized actions such as reply/forward, draft send, template send and semantic message send. Action execution returns through the canonical Email Hub runtime and context changes publish invalidation events.
Who is this for
Product Engineer
Operations Application Owner
Expected outcomes
- Source email data stays owned by Email Hub
- Connected applications receive permission-aware context and actions
Key metrics
Security impact
- Email Hub entity references, projections, relationships, timeline entries, permissions and action inputs · PII: yes where email addresses, message content, attachments, recipients, or integration payloads contain personal data
Compliance
- Context operation/resource authorization
- Trusted workspace provenance and context invalidation events
Availability & next steps
Pro
Enterprise