MyJackfruit

Help
Browse topics · Setup

Setup

← Setup

Who owns a project when several people work on it?

Short answer

Whoever made the project's vault holds it and keeps Control on it; everyone else gets only the access they are given.

Before you start

Words used here (1)
project
A project is work to bring about a change you want, such as a new app or a better way of doing something.
Deeper

A project you build on GilbPlatform is kept in a vault. A vault is the place where a person or a group keeps their records. 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. GilbPlatform alone writes the facts saying who holds a vault; no one can change them in GilbApp or from an app.

The others get what you give them when you share the vault. 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.

You can give Control to others too, and you keep yours: the owner's Control comes from holding the vault, not from a grant, so no one can take it away. A Control label on a card marked OWNER has no ×.

MyJackfruit is the public brand, at myjackfruit.com; it is not another name for GilbPlatform. Its Terms say: You own what you put in your vaults. (https://myjackfruit.com/terms/). They do not say who owns what one person writes in a vault that another person holds. If that matters for your project, write to [email protected] before you start.

GilbApp has no button that hands a whole vault over to another holder. If you need that, write to [email protected].

A vault made inside the project's vault keeps its own holder: Control on the vault around it gives no say over the vaults inside it, which may have another owner. Vaults your own AI makes from Claude Code sit inside its AI vault, a small vault that stands for your AI, and you get Read, Write and Control on each.

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:434 (Other People and Groups Access Rights), :491-493 and :525 (the owner's card: kind owner-inferred, its Control label drawn with no ×), :996 (you get Read, Write and Control on it); no control in the live build hands a vault to another holder. GilbPlatform 670005ccd64c229c59f905a00430d906781eb942 (live at https://id.gilb.com/version, read 12 November 2026): src/auth/bind-agent-vault.ts (AI vaults), src/write/ingest.ts (ownership facts written only by the system). MyJackfruit's public pages, read 12 November 2026: https://myjackfruit.com/terms/ (Last updated: November 11, 2026, Your data is yours), https://myjackfruit.com/ (Your company vault). Shared sentences word for word with the live answers Who can give access, and to whom? (Control sentences, OWNER label), How do I share a vault with a person? (the four levels), Who owns a vault's ownership facts?, How do I hand over control? (the owner's Control is not a grant), Does access given to a vault reach the vaults inside it?, How do I create another vault?, Why does my data stay mine? (MyJackfruit line, Terms quote) and What is an AI vault?.

Checked against GilbApp d529620.