Overview
Create policy-governed external access to a file or folder and revoke it when access should end.
Prerequisites
Permissions required
Steps (4)
-
1
Select the resource
Choose the file or folder that may be shared under its current File-Vault policy.
Tips
Validation
Success criteria
-
2
Configure the share
Set the supported expiry, recipient, password, domain, IP, access-limit, or download-limit controls required for the share.
Tips
Validation
Success criteria
-
3
Create the share
File-Vault authorizes the resource and creates the external share token/state.
Tips
Validation
Success criteria
-
4
Revoke when required
Use the share revoke action to terminate external access and record the change.
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.