Overview
Deliver selected File-Vault domain events to a configured HTTPS endpoint.
Prerequisites
Permissions required
Steps (4)
-
1
Choose event filters
Select the File-Vault events and resource/source filters the endpoint should receive.
Tips
Validation
Success criteria
-
2
Configure the HTTPS endpoint
Enter the target endpoint and required subscription settings.
Tips
Validation
Success criteria
-
3
Configure signing
Attach the protected signing-secret reference when signed deliveries are required.
Tips
Validation
Success criteria
-
4
Save and observe delivery
Create the subscription and monitor webhook delivery records as matching File-Vault events occur.
Tips
Validation
Success criteria
About this guide
File-Vault provides a governed workspace for files and documents. Teams use a familiar File Explorer to browse folders, search, upload, preview, download, copy, move, rename, trash, restore, share, inspect versions, and manage metadata without exposing physical storage paths.
Governance controls include document categories and types, classification, retention, download and link policies, resource ACLs, folder templates, routing rules, legal holds, audit records, security-review records, webhook subscriptions, and usage reporting. Access is evaluated through workspace permissions and File-Vault resource policy before protected operations are performed.
Other applications can use File-Vault as their secure file layer through explicit capabilities for upload planning, secure upload, binding, unbinding, search, signed delivery, folders, versions, shares, audit, reports, webhooks, and ContextResolver. Handler, RCP, and Bridge v2 converge on the same operation and resource authorization model.