Overview
Use a configured workspace provider for secure uploads, file selection, content bindings and customer-safe delivery tokens.
Capabilities
-
Requires upload options, list, upload, bind, unbind and delivery-token operations
-
Uses Core secure upload ingress before provider upload
-
Stores provider file references and content bindings while the secure-file provider owns durable file bytes
-
Supports cover media, content media and attachments
-
Requests delivery tokens only after EngagementHub visibility authorization
-
Keeps provider identity and file references available to ContextResolver relationships
Setup Steps (6)
-
1
-
2
-
3
-
4
-
5
-
6
Limitations
-
Secure file operations use the configured provider application.
-
EngagementHub stores provider/file references with its own content metadata.
-
Customer delivery follows EngagementHub content, placement and resource authorization checks.
FAQs
What does the Secure File Storage Provider integration use?
Use a configured workspace provider for secure uploads, file selection, content bindings and customer-safe delivery tokens.
How is access controlled?
EngagementHub uses workspace-scoped platform identity, configured application/provider grants, operation scopes, and resource authorization appropriate to the integration transport.
Where can administrators inspect activity?
EngagementHub exposes integration, connection, EventBus, webhook, communication and operational records through its Studio and generated operations views.
Pricing
Starter
USD 219.07 / annual
Growth
USD 730.42 / annual
Business
USD 1,460.91 / annual
Enterprise
USD 2,921.89 / annual