← Back to How do I get access to a vault someone else owns?
Does access given to a vault reach the vaults inside it?
Short answer
Read or Write given to a person on a vault reaches the vaults inside it too, except an AI vault; other access does not.
Before you start
Words used here (1)
- AI vault
- An AI vault is a small vault that stands for your AI; your AI reaches only the vaults you grant it.
Deeper
Also asked:
If I share a vault, do they also see the vaults inside it? With Read or Write on the whole vault, yes: they also reach the vaults inside it, and the vaults inside those, except an AI vault. Append and Control stay on the vault you shared.
A vault is the place where a person or a group keeps their records. A vault can sit inside another: you choose Child of an existing vault when you make it, as the answer on creating another vault shows. A child is Linked with a parent relation; still has its own name and host: it keeps its own address and is listed under its parent.
A person given Read or Write on the whole parent vault, as in the answer on sharing a vault with a person, also reaches the child, and the vaults inside that child, and the vaults inside those. The same holds for a group, several people given access together. It never goes upward: access on a vault inside gives none on the vault around it. An AI vault inside it, a small vault that stands for your AI, is left out: the access reaches it only for the person who made that AI vault.
Append, adding only, and Control stay on this vault. Whoever holds Control on a vault decides who else may read or write there; Control on a parent gives no say over the vaults inside it, which may have another owner.
Access given with Vault under SHARE WITH, which lets one vault, such as your AI vault, reach another, reaches the vault it was given on, not the vaults inside it; with Passes up hierarchy it also reaches the vaults that vault was itself given access to, but still not the vaults inside those. Passes up hierarchy does not change that: it is about reach from vault to vault through access given, not into the vaults inside; the answer on giving your AI access to a vault says more. Vaults made inside a public vault, one anyone can read, are not made public with it; each vault is made public on its own.
GilbPlatform keeps this in step when vaults move: when a vault is put inside another later, or moved under another parent, the Read and Write already given on its new parent reach it at once, and what reached it only through its old parent ends. In GilbApp today you put a vault inside another when you make it. Read or Write taken away on a vault is also taken away on the vaults made inside it, unless it was also given to them in another way.
On a vault inside another, the list under OTHER PEOPLE AND GROUPS ACCESS RIGHTS also shows the Read and Write that reach it from the vault around it, as cards like any other, without saying where they came from. Their × there does not end that access: take it away on the vault it was given on.
A vault's type, what it stands for, such as Organization or Project, gives no one access. In GilbApp you choose it when you make the vault. Later, a person with Control on the vault can change it: select the vault in Vaults and press Change type (or Set type if it has none); the platform may refuse, for example if you are not its owner. A Person vault, an AI vault and your landing vault do not offer it. A vault cannot be turned into an AI vault later, or back: make a new one.
This answer is written for a computer screen.
Source: GilbPlatform 4d008a55367a6e7453920c463a8923df37de62e9 (https://id.gilb.com/version read 2026-11-10), code read at 4d008a55: src/authz/vault-grant.ts:29-48 (a whole-vault grant on P reaches P and all its sub-vaults, a:partOf+, downward only, projected at grant and on a hierarchy change), :399-409 (vaultGrantCascades: read and write cascade; append and control FLAT, a sub-vault may have a different owner), :411-458 (an AiAgent descendant is reached only when the grantee is its mint owner), :487-547 (the slice re-derived from what remains live: a revoke keeps a descendant still reached another way); grantee a principal or a group (50-55); src/routes/vault.ts:520-546 (POST /base/vault/nest: nest + rebuildVaultGrantProjection in one transaction), :641-648 (POST /base/vault/move: stale old-ancestor rows drop, new-ancestor rows project); src/authz/vault-reach.ts:28-34 (a vault-to-vault grant reaches its named vault only, never by itself that vault's a:partOf descendants; containment propagation default off), src/authz/predicate.ts:76-116 (reach arms match the exact vault); src/authz/vault-access-edge.ts:770-799 (public vault edge: the exact vault only, grade scoped); src/authz/entity-acl.ts:492-537 (resolveDirectVaultAcl reads every grade-NULL vault_grant_projection row of this vault, which recomputeVaultGrantSlice, vault-grant.ts:500-548, writes for each descendant a Read/Write grant reaches, so the inner list shows the outer vault's person and group holders; the note at :470-476 inherited reach still excluded disagrees with the SQL; revokeVaultGrantExact, vault-grant.ts:660-705, finds no grant datom on the inner vault and returns revoked false; GilbApp VaultAccessManager.tsx:523-534 draws the × anyway), src/authz/vault-reach.ts:8-35 (full edges chain onward), src/routes/consent.ts:107-133 (GET /base/consent/vault-acl serves it); src/routes/vault.ts:419-470 (POST /base/vault/set-represents: owner only, to or from t/AiAgent refused). Developer guide docs/BASE-DEVELOPER-GUIDE.md §5.4 :5016-5047, §5.4.1 :5049-5094 (four modes; control confers no read and no write), §5.4.2 :5096-5135 (vault nesting, the AiAgent refusals, set-represents cannot flip to t/AiAgent, vault-and-descendants reach). GilbApp af0f04ee838a4d55887d2ff1f72edd49a4ff7ca0 (https://gilb.com/app/version.json): src/components/VaultAccessManager.tsx:639 (Vault-to-vault reach…), :728-746 (Stops here, Passes up hierarchy, and the lines Vaults that can reach the grantee inherit this access onward. / Only the grantee vault gets this access — no inheritance.); src/lib/base/createVault.ts:42 (a:podRepresents written at create only; no GilbApp call of set-represents, the code shows:52Z); src/admin/MoveVaultDialog.tsx (moving is an admin dialog). GilbVeda t:PartOf (Approved), t:ControlMode (Suggested), public read. Shared sentences word for word: vault gloss; A child is …; Append and Control stay on this vault; Control sentence; AI vault gloss; group gloss; Vaults made inside a public vault …; Read or Write taken away …; type sentence and A vault cannot be turned into an AI vault later, or back: make a new one..
Checked against GilbApp d529620.