docs: detail managed accounts

This commit is contained in:
thePR0M3TH3AN
2025-07-07 22:01:54 -04:00
parent 127729e1e2
commit eefe4d9ca5
3 changed files with 33 additions and 6 deletions

View File

@@ -95,6 +95,8 @@ Each entry is stored within `seedpass_entries_db.json.enc` under the `entries` d
- **origin** (`string`, optional): Source identifier for imported data.
- **value** (`string`, optional): For `key_value` entries, stores the secret value.
- **index** (`integer`, optional): BIP-85 derivation index for entries that derive material from a seed.
- **word_count** (`integer`, managed_account only): Number of words when deriving the child seed (12 or 24).
- **fingerprint** (`string`, managed_account only): Identifier of the child profile, used for its directory name.
Example:
```json
@@ -267,6 +269,11 @@ Each entry is stored within `seedpass_entries_db.json.enc` under the `entries` d
}
```
Managed accounts store a child seed derived from the parent profile. The entry is saved under
`.seedpass/<parent_fp>/accounts/<child_fp>` where `<child_fp>` is the managed account's
fingerprint. When loaded, the CLI displays a breadcrumb like `<parent_fp> > Managed Account > <child_fp>`.
Press **Enter** on the main menu to exit back to the parent profile.
The `key` field is purely descriptive, while `value` holds the sensitive string
such as an API token. Notes and custom fields may also be included alongside the
standard metadata.