Asset Management

An asset belongs to one team. Its Name, Website, and Instructions are unencrypted metadata. Secret text and attachment contents are encrypted in your browser to the asset's recipients. Attachment names, MIME types, and sizes remain visible.

Do not put passwords, recovery codes, or other confidential content in names or instructions. Team members and the service can read those fields while identities are locked.

Create an asset

1. Open the team dashboard and unlock your personal identity.
2. Select New Asset.
3. Enter a name and optional website or instructions.
4. Enter secret text and select attachments if needed.
5. Select Create Asset.

You become the asset's Custodian. The browser encrypts each secret and file to your public key, plus the team owner's key if owner escrow is enabled. Subsequent recipient sets include enrolled Successors. Zero-recipient encryption is rejected.

Files are limited to 10 MiB each, 20 per asset, and 64 MiB per encrypted request. Armoring increases payload size. Executable file extensions are rejected by the editor.

Browse and view content

The dashboard lists assets alphabetically even while your identity is locked. Select an asset to see its website, instructions, guardian assignments, and attachment metadata.

To view secret text, unlock your identity and select View Secret. To save files locally, select Download for a file or Download Attachments for all files. Both actions fetch ciphertext through the same server permission gate, including attachment-only assets, and decrypt it in the browser. Existing access notifications apply.

Custodians have payload access. Successors need an approved access request. Gatekeepers do not receive payload access through their guardian role. See Access Requests.

The secret dialog supports Copy to Clipboard. Close it when finished. Clipboard contents and downloaded files remain outside the application's control after locking.

Edit metadata or encrypted content

1. Open the asset and select Edit.
2. Change metadata directly. Opening the editor does not fetch secret or attachment ciphertext.
3. To change encrypted content, unlock your identity and select Edit Secrets. This performs the gated payload read and decrypts the complete payload.
4. Edit the secret or add/remove attachments.
5. Select Update Asset.

A metadata-only save preserves existing ciphertext, recipient fingerprint, and payload version. An encrypted save replaces the complete secret and attachment set with a version check. If another user edits the asset or changes its recipients, refresh and retry rather than overwriting their work.

Unsaved changes

Secrets and selected file bytes stay in memory until saved. Secret drafts are not auto-saved to local storage. Old persisted asset drafts are purged. Closing the editor, refreshing, locking, expiration, logout, or an account change can discard unsaved work and clears displayed plaintext. Save before leaving the editor.

Keep recipients current

Adding or removing a Successor changes the expected recipient keys. An unlocked Custodian attempts to re-encrypt after a guardian change. Gatekeeper changes do not change encryption recipients. Owner escrow changes can also require re-encryption.

An asset marked Needs re-encryption has an outdated recipient fingerprint or a recipient who has not enrolled. An eligible Custodian or approved Successor who can decrypt can repair it. If you receive a decryption error, ask an eligible recipient to repair the payload; server approval alone cannot make an old ciphertext decryptable by a newly enrolled identity.

Repair preserves the existing secret's presence and every attachment's name, type, size, and count. It cannot silently drop inaccessible or undecryptable content. Removing a recipient affects future ciphertext, not previously obtained copies.

Legacy assets

Assets marked for migration must be converted before encrypted editing or identity rotation. The legacy phrase is used locally for decryption; eligible users then save age ciphertext to the current recipients. The owner finalizes the team migration only after all legacy secrets and attachments are converted. Ownership does not bypass asset-access gates. See Legacy migration.

Delete an asset

Select Delete on an asset you can manage, then confirm the deletion. Deletion removes the stored metadata and encrypted content permanently. Download needed files or copy secret text into a secure backup first.

There is no automatic cross-team move. To recreate an asset in another team, decrypt it with authorized access and create a new asset encrypted to that team's recipients. Review guardians again in the destination team.