Entries

An entry is one secret — usually a login — and it always lives inside a collection. With no collection yet, Entries says so and there is nothing to create; start by creating a collection.

Entries lists what you can open, grouped by the collection it lives in and nested the way your collections are. A collection with no entries is listed all the same — it is there to put something in. Press a collection's name to fold it away with everything under it; a folded one says how many entries it is hiding, which is not the same as being empty. What you fold is remembered in this browser only, and everything starts unfolded.

The arrow keys walk the list: up and down move between rows, right opens a collection or steps into it, and left folds it or goes back to the one it hangs from. Enter opens the entry you are on.

Create an entry

1. In Entries, press New entry.
2. Choose the collection. It decides who can open the entry.
3. Fill in Name, and optionally Password and the URL of the site.
4. Press Save entry.

Generate one, under the password, fills it with a strong random one. You can also fill in a username, a note and a one-time code seed while creating the entry, and add any other field afterwards.

Find an entry

Type in Search. The search runs in your browser, over what is already decrypted — the server cannot search your secrets because it cannot read them. Each result shows its collection and which fields it has. While you are searching, the results are a plain list of matches rather than the grouped one: what matched is what you came for, not the branches it sits under. Empty the box and the grouping comes back, folded the way you left it.

Public and secret fields

The username and the note are shown as soon as you open an entry. Every other field is secret and shows as •••••••• until you press Reveal.

One field is revealed at a time — revealing another hides the one before it — and a revealed value hides itself after twenty seconds. Hide puts it back at once, and so does saving a change. It is the same twenty seconds as the autofill screen on the phone.

Copy

Every field has Copy, and copying does not need revealing. The value goes to your system clipboard, and the app does not clear it afterwards: anything that reads your clipboard later can read it. If the browser refuses the clipboard, reveal the value and copy it by hand.

Reveals and copies are recorded in the account's activity, marked as reported by your browser.

One-time codes

An entry with a one-time code shows it under One-time code, with the seconds it has left and its own Copy. The code is copied without the space, ready to paste. Paste the otpauth:// link or the seed itself when creating the entry, or add the field later. Only the seed is kept: a link that asks for a different number of digits or a different period falls back to the usual six and thirty seconds.

Change a field

Press Change it next to the field, type the new value and Save. You change one field at a time. If someone changed the same field since you opened it, the app keeps both versions and asks you to choose in the history. Rename, next to the entry's name, changes the name; Add a field adds one, with a name of your own if none of the usual ones fits; Remove takes a field away. Under URLs you can add, change and remove them, and choose when each one matches.

History

History next to each field shows every version, marked current, older or conflict. Restore brings an older one back; on a conflict you choose Keep this or Keep current. Choosing always adds a version — nothing is overwritten, and the losing version stays until the account's retention removes it.

Seeing the history and restoring are permissions of their own, separate from view and edit: whoever manages the collection grants them, and manage has both. Without History, someone who can edit still sees the current value and a conflict to resolve — nothing older — and nobody else sees the history at all.

If your permission is use

With use on a collection you can copy and fill its entries, but not see or change the values. It reduces exposure; it is not a cryptographic boundary — the browser does hold the value.

“◷ rotation pending”

This mark appears when someone who could open the entry lost access. They may still have a copy, so change the password on the site and then here.

Deleting

Delete entry, at the bottom of an entry, sends it to the trash with its fields and URLs. It needs edit or manage on the collection, and it asks first.

It can be undone: the entry stays in the Trash, at the bottom of Collections, and Restore brings it back with its fields — see The trash. Meanwhile nobody sees it, and every device drops it on its next sync. What does not come back is a copy that already left, exported or written down elsewhere: if the password was in use, change it on the site.

Deleting a collection deletes the entries in it, in one step. See Collections and sharing.

Passkeys for websites

New passkey creates a key pair for a site and keeps the private half in the vault; the app shows the public key to register on that site. Signing in to a website with a stored passkey is not available yet, in any of the apps.