Overview
Upload files through File-Vault so security, document metadata, folder routing, versions, and audit state are applied consistently.
Problem
Applications and users need a controlled ingress path instead of writing directly to storage.
Solution
Resolve upload options and accept bytes through the platform secure-upload boundary before creating File-Vault records.
How it works
File-Vault evaluates the intended document and destination, accepts the file through SecureUploadService, creates file/document/version state, and records audit and events.
Who is this for
Workspace User
Application Engineer
Expected outcomes
- One secure ingress path for users and trusted applications
- Consistent file, document, version, and audit state
Key metrics
Security impact
- Uploaded file bytes, file metadata, document metadata, source references, and security state · PII: yes where uploaded content or metadata contains personal data
Compliance
- Workspace permission, operation authorization, upload policy, secure-file controls, audit, and resource policy
Availability & next steps
Starter
Business
Enterprise