Vault¶

The vault holds records: key/value entries everything else points at. A share never copies a record — it references it, so editing the value here changes what every share of it resolves to, immediately.

Records¶

A record is a key, a value, a label, a type and a format.

The type drives how the app renders and validates the value; under the hood everything but a file is stored as text, capped at 1000 characters.

The format is default or hidden — a hidden value is masked on screen until you reveal it. Use it for passwords, tokens, anything you don't want readable over your shoulder. For file records, hiding masks the file name.

Files¶

A file record stores one upload. You can replace the file in place and rename what a downloader sees — the name is a label, never a path. Whether uploads are allowed and how large they may be is the operator's choice.

Aliases¶

A record can point at another record instead of holding its own value, and it resolves the parent's current value at read time. This is how you answer someone's requested key with data you already hold: the alias carries the key they asked for, the value stays in one place.

Sections¶

A section is a named group of records — "Banking", "Onboarding pack" — that can be created, renamed, duplicated, and shared as a unit. Sharing a section shares its current membership: add a record to it later and existing shares of the section pick it up.

Starting from a template¶

New → From template materialises a whole set of sections and records in one step — useful when every client or project gets the same structure. Templates are also what give requests their shape; authoring them is covered in Templates.