Capability-Based Delivery Providers — Integration

Overview

Bind workspace applications that satisfy AccessGuard outbound roles for email, SMS, voice, WhatsApp, push, and case/problem operations.

Capabilities

• Provider discovery through system.capabilities and handler metadata

• Role-specific required and optional capability checks

• Bridge credential minting and configuration

• Remote connection status, update, bulk status, and deletion administration

• Provider secret references protected through Core AppSecretService-backed credential services

1. 1

   Step 1

   Open the AccessGuard outbound integration catalogue.

   Back to top
2. 2

   Step 2

   Choose the delivery or case/problem role.

   Back to top
3. 3

   Step 3

   Probe installed applications and select one satisfying the required capabilities.

   Back to top
4. 4

   Step 4

   Bind the role and store the connection metadata/secret references.

   Back to top
5. 5

   Step 5

   Run a test operation and inspect AccessGuard connection/log state.

   Back to top

Limitations

• A provider must satisfy the capability contract for the role before it can be bound.

• AccessGuard authorization, communication policy, and source provenance remain separate from the provider’s delivery implementation.

FAQs

Pricing