alee/relicario
1
0
Fork 0
Code Issues Pull Requests 8 Actions Packages Projects Releases Wiki Activity

docs(user): org item-type parity shipped — flip concepts + faq org sections

Browse Source 
All four v0.8.1 streams merged (main 4c0a289): org add now supports all 7 item
types (card/key/totp/document) and org edit is interactive. Flip the two
high-level org sections from "coming" to shipped, grounded in the real merged
`relicario org add <type> --collection …` surface; remove the rebase TODO markers.
This commit is contained in:
adlee-was-taken
2026-06-20 21:59:54 -04:00
parent 2ea98f3aba
commit d0f757b66d
2 changed files with 3 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
user_docs/concepts.md
View File

@@ -54,9 +54,7 @@ Most people use a **personal vault** — one vault, one person, one set of two f
Relicario also supports a **multi-user org vault** for teams: an owner can add members, create collections (groups of items), and grant or revoke access per collection. Roles (owner, admin, member) control what each person can do, and every action is recorded in a signed audit log. The same trust model applies — the server only ever sees ciphertext, and access is enforced by collection grants, not by server-side permissions. Relicario also supports a **multi-user org vault** for teams: an owner can add members, create collections (groups of items), and grant or revoke access per collection. Roles (owner, admin, member) control what each person can do, and every action is recorded in a signed audit log. The same trust model applies — the server only ever sees ciphertext, and access is enforced by collection grants, not by server-side permissions.
Org vault support is actively evolving. Item-type parity (Card, Key, Document, TOTP) in the org vault is coming soon. An org vault stores the same seven item types as a personal vault — logins, secure notes, identities, cards, keys, documents, and TOTP codes — added with `relicario org add <type> --collection <name> …`. Members only ever see the collections they have been granted.
<!-- TODO: revisit org item types after rebase on final main -->
For day-to-day use, see [Sync & backup](sync-and-backup.md) for syncing an org vault across devices. For day-to-day use, see [Sync & backup](sync-and-backup.md) for syncing an org vault across devices.

6
user_docs/faq.md
View File

@@ -60,11 +60,9 @@ Install is currently build-from-source (no web-store listing). See [The browser
## Can my team share a vault? ## Can my team share a vault?
Relicario includes an org vault feature (`relicario org …`) with owner/admin/member roles, collections, per-collection access grants, and a signed audit log. The server only sees ciphertext; access is enforced by collection grants. Relicario includes an org vault feature (`relicario org …`) with owner/admin/member roles, collections, per-collection access grants, and a signed audit log. It supports the full set of item types — logins, secure notes, identities, cards, keys, documents, and TOTP — added with `relicario org add <type> --collection <name> …`. The server only sees ciphertext; access is enforced by collection grants.
**Current limitation:** the browser extension does **not** yet support org vaults — there is no org switch, browse, or write support in the extension. Org vault access is CLI-only for now. Additionally, org `add` currently supports login, secure-note, and identity items; Card, Key, Document, and TOTP parity for the org vault is coming in the next release. **Current limitation:** the browser extension does **not** yet support org vaults — there is no org switch, browse, or write support in the extension. Org vault access is CLI-only for now.
<!-- TODO: revisit org item types after rebase on final main -->
--- ---