MyJackfruit

Help
Browse topics · Working together

Working together

← Working together

What can a person I invite see and do?

Short answer

They see and do what their level allows: Read reads the vault, Write + Read also writes, Append only adds, Control manages access.

Deeper

Also asked:

What can a helper see and change? What their access allows: with Read they see every record and file in the vault; with Write + Read they can also add, change and delete records. Without Control they cannot give anyone access.

Why do I see vaults that I did not make? Usually because someone shared them with you: a vault shared with you shows in your own vault list, and with Read or Write so do the vaults made inside it. A record shared with you also brings its vault into your list.

What do Read, Write, Append and Control mean? Read lets a person read the vault; Write + Read also lets them write to it; Append lets them only add, not read or change; Control lets them manage who else has access, with no Read or Write by itself.

Which access should I give a friend who helps me? Give Read if they only need to look, or Write + Read if they help change the project. Keep Control for yourself unless they must manage access: whoever holds it can copy the whole vault and give themselves Read or Write.

Why can't I change anything in this vault? It says I hold only Read. With Read you can look but not save, so GilbApp says You hold read only on the vault, so nothing can be saved here. Ask someone who holds Control on it to give you Write + Read.

If I give a person Write, can their AI write in my vault too? In GilbApp's chat, yes: their AI works as them, with their access. An AI they connected with ▸ CONNECT AI reaches your vault only if someone holding Control there gives its AI vault access.

You invite a person by sharing a vault with them; the answer on sharing a vault with a person shows how. A vault is the place where a person or a group keeps their records. You find the person by their vault name or vault address, so they need an account of their own first. When you give access, The person gets this vault in their own vault list. GilbPlatform sends them no e-mail about it, so tell them yourself.

You choose one of four levels for them. Read lets the person read the vault. Write + Read lets them read it and also write to it (GilbApp grants Read first, then Write). Append lets them add to the vault only, not read or change what is there. Control lets them manage who else has access (grant and take it away). 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.

With Read they see every record and file in the vault. GilbPlatform lets anyone who may read a vault read what it holds, unless an entry carries its own sharing level, as My Note does: My Note on a card in your own vault is for you alone. Sharing a vault with Read or Write also shares the vaults made inside it, except an AI vault, a small vault that stands for your AI; Append and Control stay on this vault.

With Write + Read they can also add, change and delete records. GilbPlatform never writes over a fact: a change closes the old fact and adds the new one. Deleting ends a record; it does not erase it.

What they cannot do without Control: give anyone else access, their own AI included, take a copy of the whole vault, or give up their own access; holding Read, Write or Append lets you give access to no one. The agent they chat with in GilbApp works as them, with their own access. For their own AI, such as Claude Code, to work in your vault, someone who holds Control there gives its AI vault access, as the answer on giving your AI access to a vault shows.

You can change your mind at any time: taking access away works from the person's next request. The answer on taking access away shows how.

This answer is written for a computer screen.

Source: GilbApp 96968de7c3e3e685296f20a2599cbc8d305c9ea7 (live at https://gilb.com/app/version.json, read 12 November 2026): src/components/VaultAccessManager.tsx:638 (The person gets this vault in their own vault list.), :434 (Other People and Groups Access Rights); src/components/VaultDetail.tsx:320 (Download a copy of this vault, shown only to a Control holder). GilbPlatform 670005ccd64c229c59f905a00430d906781eb942 (live at https://id.gilb.com/version, read 12 November 2026): src/routes/authz.ts (the grant routes send no e-mail; e-mail is sent only by the sign-in code path, src/auth/send-otc-email.ts). Shared sentences word for word with the live answers How do I share a vault with a person? (the four levels, word for word; the vault-list line; the vaults-inside sentence), Who can give access, and to whom? (Control sentences; lets you give access to no one), How do I keep a stakeholder's contacts private? (sharing level and My Note), Why does my data stay mine? (never writes over a fact), How do I give my AI access to a vault? (the agent in GilbApp works as you), How do I take access away?, How do I leave a vault someone shared with me?, What is an AI vault?. Live help pages How do I share one record (not the whole vault)? (the record's vault shows in their list) and Can a developer or a friend help me? (Control: keep it for yourself unless they must).

Checked against GilbApp d529620.