Overview
Grant an installed workspace application explicit File-Vault operations and trusted transports.
Prerequisites
Permissions required
Steps (4)
-
1
Open inbound integrations
Open File-Vault integration administration and choose the workspace application.
Tips
Validation
Success criteria
-
2
Probe capabilities
Use trusted discovery to validate the application capability contract.
Tips
Validation
Success criteria
-
3
Select operations and transports
Choose the File-Vault operations and Handler/RCP or scoped Bridge access required by the integration.
Tips
Validation
Success criteria
-
4
Save and verify
Persist the File-Vault application grant and perform an authorized capability call.
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.