Overview
Authorize installed workspace applications to discover Email Hub capabilities and invoke account, compose, semantic-message, template, Bridge, and context operations through trusted Handler or RCP execution.
Capabilities
-
system.health and system.capabilities discovery
-
accounts.suggest, compose.send, messages.send, templates.suggest, templates.send, and template-versions.suggest
-
Per-application operation grants and transport authorization
-
Resource checks for sender accounts, drafts, templates, versions, message bindings, Bridge connections, and context entities
-
Trusted caller provenance and delegation-aware authorization
Setup Steps (5)
-
1
-
2
-
3
Step 3
Choose the Email Hub operations and Handler/RCP transports that application may use.
-
4
-
5
Step 5
Invoke the approved capability and verify the resulting Email Hub operation state.
Limitations
-
Authority is workspace-scoped, application-scoped, operation-scoped, transport-scoped, and resource-scoped.
-
Mutating capability calls execute through the canonical Email Hub runtime and retain trusted inter-app provenance.
FAQs
Which trusted transports are supported?
Email Hub capability definitions support Handler and RCP, with Bridge available on operations that declare a Bridge scope.
Can one application act on behalf of another?
Delegated calls are evaluated against trusted provenance and explicit Email Hub delegation authorization before the requested resource operation executes.
Pricing
Starter
USD 219.07 / annual
Pro
USD 584.32 / annual
Enterprise
USD 1,095.66 / annual