Loading…
Velaxe
File-Vault — Secure File Explorer, Document Governance, Sharing & Audit | Velaxe

File-Vault

Manage file versions

Inspect version history, create a new version, and restore a prior File-Vault version when authorized.

10 min Beginner Workspace User, Document Administrator Updated Aug 24, 2026

Overview

Inspect version history, create a new version, and restore a prior File-Vault version when authorized.

Prerequisites

None.

Permissions required

filevault.explorer.version.view filevault.explorer.version.create filevault.explorer.version.restore

Steps (4)

Estimated: 10 min
  1. 1

    Open version history

    Workspace User 2 min Back to top

    Select the file and open its File-Vault version history.

    Tips

    —

    Validation

    —

    Success criteria

    —

  2. 2

    Inspect versions

    Workspace User 2 min Back to top

    Review available version metadata before choosing a version operation.

    Tips

    —

    Validation

    —

    Success criteria

    —

  3. 3

    Create or select a version

    Workspace User 3 min Back to top

    Add the governed next version or select the historical version to restore.

    Tips

    —

    Validation

    —

    Success criteria

    —

  4. 4

    Restore when needed

    Workspace User 3 min Back to top

    Run the authorized restore workflow and confirm the canonical file now references the restored state.

    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.