Collaboration: Secure Workspace Sharing

The central dilemma of zero-knowledge storage: how can distributed teammates co-author, comment, and exchange files without disclosing their master private keys?

1. Asymmetric Key Encapsulation (KEM)

When you share an encrypted workspace folder with a coworker, your local client requests the coworker's public identity key (certified via an out-of-band identity ledger or PGP web of trust). Your client creates an ephemeral 256-bit AES folder key, wraps that key using the colleague's public key (e.g., via Kyber or X25519), and transmits the wrapped key to the server.

At no point does the storage host receive the plaintext folder key. The recipient decrypts the wrapped key locally using their private credentials, gaining granular access exclusively to the shared directory.

2. Ephemeral Zero-Knowledge Link Sharing

Distributing files to external clients who do not possess a cryptographic account requires URL fragment isolation:

3. Workspace Access Control Matrix

Our lab evaluates enterprise sharing tiers based on role isolation, audit log integrity, and cryptographic revocation efficiency.

Sharing Architecture Key Revocation Speed Host Knowledge External Guest Support
Direct Public Key Exchange Immediate (Lazy Re-keying) Zero (Ciphertext Only) Requires Client Key Pair
URL Anchor In-Browser Decrypt Immediate Expiration Zero (Key in URI Hash) Universal Web Browser
Server-Mediated RBAC (Legacy) Instantaneous Total Plaintext Access Universal Account
Compare Pricing & Provider Benchmarks →