# Who can give access, and to whom?

Checked 2026-11-15 against GilbApp d5296208bbffa2ab70076e6194f5537c4be1ddf7.

Only someone who holds "Control" on a vault can give access there, to a person or another vault, or let everyone read it.

## Deeper

A vault is the place where a person or a group keeps their records. Whoever holds "Control" on a vault decides who else may read or write there. "Control" gives no "Read" or "Write" by itself, but whoever holds it can take a copy of the whole vault, every record and file, and can give themselves "Read" or "Write". When you make a vault, you can read and write in it from the start, and you hold "Control" on it, so you decide [who else gets access](http://support.gilb.com/help/how-do-i-share-a-vault-with-a-person).

Someone who holds "Control" on a vault can give it to you: it is one of the four levels under "ACCESS" in "▸ GRANT ACCESS". You can then give and take away access on that vault too, but only there: "Control" on one vault gives you no say over any other. The owner keeps theirs: a "Control" label on a card marked "OWNER" has no "×".

Holding "Read", "Write" or "Append" \(adding only\) lets you give access to no one. Nor can access be added by editing a record: GilbPlatform refuses such a change, and gives access only by the act of granting it, which checks for "Control" first. The same holds for [one record shared on its own](http://support.gilb.com/help/how-do-i-share-one-record-not-the-whole-vault): only the vault's owner or a holder of "Control" on that vault can share it. GilbApp may show its sharing controls to someone who can only write there; GilbPlatform then refuses the share.

GilbPlatform takes four kinds of receiver and no others: a person, a group \(several people given access together\), another vault, and, for reading only, everyone. Anything else is refused, not stored. Everyone means anyone, signed in or not; nobody can be given writing that way.

In GilbApp today, "▸ GRANT ACCESS" offers "Person" and "Vault" under "SHARE WITH", and "Make public" for everyone; it has no choice for a group. For a vault there are only "read" and "write", given one at a time; "Append" and "Control" are offered only for a person. Your AI [gets access](http://support.gilb.com/help/how-do-i-give-my-ai-access-to-a-vault) through "Vault": it acts as its AI vault, a small vault that stands for your AI.

No one can be given reading or writing in an AI vault: GilbPlatform refuses it. In GilbApp a vault cannot be given access to itself either; GilbApp then says "A vault cannot grant access to itself."

A computer added to your account with gilb-computer add, a command run on that computer, can make things public or private and take access away, but cannot give access to a named person, group or vault; GilbPlatform answers that this is done in GilbApp. [The answer on removing a computer from your account](http://support.gilb.com/help/how-do-i-remove-a-computer-from-my-account) says more about such computers.

GilbPlatform's developer guide names one exception still in its code: the account that runs GilbPlatform can add a person to a group, who then gets what that group was given, and can cut a person off everywhere, without "Control" on a vault. The guide says this is to be removed.

The same "Control" takes access away; [the answer on taking access away](http://support.gilb.com/help/how-do-i-take-access-away) shows how. [Giving up your own access](http://support.gilb.com/help/how-do-i-leave-a-vault-someone-shared-with-me) needs it too: where you hold "Control" on a vault someone shared with you, each of your labels under "YOUR ACCESS RIGHTS" in its pane has an "×" that gives it up. With only "Read", "Write" or "Append" you cannot give it up yourself; someone who holds "Control" there takes it away.

Source: GilbPlatform 4d008a55 \(https://id.gilb.com/version read 2026-11-10, dirty false\), code read at 4d008a55: src/routes/authz.ts:20-37 \(vault-scoped grant and revoke gate on requireControlHolder: owner or delegated Control; "acl:Control is ACL-management ONLY — it confers NO data read/write reach"\), :604-640 \(requireControlHolder\), :1411-1421 \(grant-vault: "the gate confines them to vaults they Control ... never reaches another vault"; mode=control delegates Control\), :1483-1500, :1573, :1638-1639, :1675-1676 \(whole-vault, vault-reach and public grants all Control-gated\), :436-470 \(requireDirectGrantAuthority: "requires the vault's holder or a Control holder"\), :925-935 \(everyone is a legal READ grantee on one item; only that may be granted by a computer token\), :774, :901, :1190, :1245 \(assertNotAiAgentDataTarget: no grant into an AI vault\); src/authz/grantee-uri.ts:116-151 \("Three shapes, and no others" — principal, group; "Refused rather than stored raw"\); src/auth/app-standing.ts:230-246 \("a computer may publish, unpublish and revoke access, but may not &lt;act\>; do this in GilbApp"\); src/write/ingest.ts:1720-1768 \(a non-owner write may not assert a grant attribute, except a self read-back on create and an unchanged re-assert\); src/auth/create-named-vault.ts:220-223 \("The name holder's read, write and control are written there"\). Developer guide docs/BASE-DEVELOPER-GUIDE.md at 4d008a55: §5.1 lines 4883-4886 \(the OWNER\_PRINCIPALS path "is owed removal"\), 4907-4936 \(rules 4 and 5: Control is a grant on a vault; Control confers ACL-management only; the grant-attribute guard\), 4940 \("A write grant also grants read"\), 4946-4951 \(the three gates; membership, revoke-member, revoke-principal keep requireOwner\), 4964 and 4967 \(anything else → 400; t/PublicGrantee → 400 on write: no public write\); §5.6 lines 6010-6013 \(ensureOwnerSelfGrant seeds whole-vault read and write at provision\). GilbApp af0f04ee \(https://gilb.com/app/version.json read 2026-11-10\): src/components/VaultAccessManager.tsx:610-617 \("Share with", CSS capitals, chips "Person" and "Vault"; no group chip\), :284 \("A vault cannot grant access to itself."\), :702 \("Write + Read"\). Rows: Capability.Security.OnlyHoldersMayGrant, GrantToValidGranteesOnly, OwnVaultGivesYouReadAndWrite.
