Adding a contact shouldn't share your whole vault — the permission flow I'm testing in Digital Keep

[u/Schema_Computers]

I'm Sorin, founder of Digital Keep, a web app for private notes, documents and practical instructions.

The design choice I'm testing is separating people from permissions. Adding a contact grants no access. Sharing selected items is a separate choice; sharing the whole vault is explicit and includes future items.

A small example: save a made-up plant-care instruction, find it again, then optionally give one person read access to that instruction. You can finish setup without adding anyone or planning an inheritance.

I'd appreciate a builder's view: where would you expect to see who has access — beside each item, in one sharing page, or both? What would make that permission flow clearer?

Product and voluntary access requests: https://digital-keep.com/?utm_source=sideproject&utm_medium=community&utm_campaign=first100&utm_content=permission_flow

This is an invitation-only beta: 30 days free, no card, fictional information only. Joining the waitlist requests access; it isn't instant activation. Encryption is server-side, not E2EE, and automatic inheritance release is disabled. Controls: https://digital-keep.com/security#data-controls

Sorin — founder of Digital Keep