Overview
Upload content through File-Vault so its destination, document metadata, secure ingress, version state, and audit are handled consistently.
Prerequisites
Permissions required
Steps (4)
-
1
Choose the destination
Select the target folder or provide the governed document/source context required for upload planning.
Tips
Validation
Success criteria
-
2
Resolve upload policy
File-Vault evaluates applicable file/document metadata, MIME/size policy, routing, folder, and access inputs.
Tips
Validation
Success criteria
-
3
Submit the file
Send the file through the File-Vault upload operation so the platform secure-upload boundary accepts the bytes.
Tips
Validation
Success criteria
-
4
Use the resulting file
Use the returned File-Vault file reference for preview, delivery, versions, binding, sharing, or other authorized operations.
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.