Overview
Attach a File-Vault file to the authoritative business object after its final object identifier is known.
Prerequisites
Permissions required
Steps (4)
-
1
Upload the file
Create the File-Vault file through the governed upload operation and retain its file id.
Tips
Validation
Success criteria
-
2
Create the source object
Complete the source application transaction that creates the authoritative business record.
Tips
Validation
Success criteria
-
3
Call files.bind
Bind the file to the authenticated source application, object type, and object identifier.
Tips
Validation
Success criteria
-
4
Use the bound reference
Store or display the File-Vault reference through the source application workflow.
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.