Choose the snapshot
Select the supported record and explicitly approve attachment disclosure where applicable.
← All features
Encrypted Sharing
Share a deliberate snapshot—not the keys to your workspace.
Publish controlled Note, Docs, or Canvas snapshots with fragment-held keys, revocation, regeneration, and explicit attachment disclosure.
Purpose
Why Encrypted Sharing exists.
Sharing creates a narrow distribution boundary around selected content. The live private record and its canonical Files remain separate.
PRODUCTIVITY EFFECTDeliver useful work without exporting the entire workspace or maintaining an uncontrolled duplicate document.
How you will use it
Useful from the first action to the next.
Publish separately
The client creates a read-only encrypted snapshot and keeps the decrypting key in the URL fragment.
Stay in control
Regenerate, republish, change download permission, or revoke the link.
In real work
Different roles. A specific advantage.
These examples show how the same feature can remove a different kind of friction depending on the work around it.
Freelancer
Send a client-ready document without opening the underlying workspace.
Student
Share a polished note or diagram while keeping other study material private.
Engineer
Publish a selected architecture Canvas without exposing source Files by default.
Data & privacy
What it uses. What it stores. Where the boundary sits.
Only the snapshot content, assets, and permissions you choose to publish.
A separate encrypted snapshot and operational publication state—not a live plaintext mirror.
The fragment-held key is not sent to the API. Anyone holding a valid capability link can access that published snapshot.
Connected system
Encrypted Sharing becomes more useful beside…
Make it part of one system
Start with Encrypted Sharing. Connect the rest when it helps.
No imported complexity. No privacy compromise.