# Can several people work on the same project?

Checked 2026-11-15 against GilbApp d5296208bbffa2ab70076e6194f5537c4be1ddf7.

Yes: share the project's vault with each person; each signs in with their own account and can use their own AI.

## Deeper

Also asked:

Can multiple people work on the same project? Yes: [share the project's vault with each person](http://support.gilb.com/help/how-do-i-share-a-vault-with-a-person); each signs in with their own account and can use their own AI. Several can work at the same time, so agree who works on which part.

Can someone else help me write the plan? Yes: give them "Write + Read" on the project's vault. They can then change the plan, and their Kai-Zen can work on it too. Agree who asks Kai-Zen to change the plan.

Can I see who changed what in the plan? Not in GilbApp today: "▸ DETAILS" on a record shows when it last changed, not who changed it. GilbPlatform keeps who wrote each fact, and programs can read that history.

Can two people share one account? Do not: an account is one e-mail address, and whoever signs in with it acts as you, with all your access. Give each person their own account and share the vault with them.

A project is kept in its own vault, the store for its records, so you share the project by sharing that vault. Whoever holds "Control" on a vault decides who else may read or write there; you hold it on a vault you made. The answer on sharing a vault with a person shows each step, with pictures: you pick the person and their access. "Write + Read" lets them read the project and change it; "Read" lets them read it only. Each person [signs up](http://support.gilb.com/help/how-do-i-sign-up) and signs in with their own account. Holding "Read" or "Write" lets a person give access to no one.

Each person can use their own AI, in two ways. In GilbApp's chat, a person's AI works in the vaults as that person, with that person's access: once you have given them access, their Kai-Zen can work on the project too. An AI connected on their computer with "▸ CONNECT AI" acts as its own AI vault, a small vault that stands for that AI, so the project's vault must give that AI vault access. Only someone who holds "Control" on the project's vault can: the other person sends you their AI vault's address, and you [give it access](http://support.gilb.com/help/how-do-i-give-my-ai-access-to-a-vault) with "Vault" under "SHARE WITH". Each person's AI runs on their own subscription.

Several people can work in the vault at the same time. When two change the same record, GilbApp checks in the plan and on a person's card, and the person who saves second sees a message such as "This record changed elsewhere. The latest is shown; your change to a field that was also changed there was not saved." or, on a card in the plan, "This changed elsewhere. The card now shows the latest; your change was not saved." Then make your change again. For some changes, such as a process step or a sharing change, GilbApp does not check, and the later change stays. So agree who works on which part, and who asks Kai-Zen to change the plan. Before it does anything, Kai-Zen reads the project's setup, its specs and its last round of work, so it starts from what the others saved.

GilbPlatform keeps every earlier version of a record, with when each fact, one value in one field, was written and who wrote it. GilbApp has no screen for that history today: "▸ DETAILS" on a record shows when it last changed, not who changed it. Programs can read the history; [the answer on seeing a record as it was before](http://support.gilb.com/help/how-do-i-see-a-record-as-it-was-before-its-history) says more. What an AI connected with "▸ CONNECT AI" writes is written as its AI vault; what an AI writes from GilbApp's chat is written as the person who uses it.

To stop someone working on the project, [take their access away](http://support.gilb.com/help/how-do-i-take-access-away); that has its own answer.

This answer is written for a computer screen.

Source: GilbApp 96968de7 \(live at https://gilb.com/app/version.json, read 12 November 2026\): src/components/records/RecordDetail.tsx:1233-1236 \("This record changed elsewhere. The latest is shown; your change to a field that was also changed there was not saved."\), :1254-1257; src/components/records/PlanStakeholders.tsx:72, src/components/records/PlanTagLinks.tsx:177, src/components/records/valueChildRecords.ts:190 \("… changed elsewhere. The card now shows the latest; your change was not saved."\); src/lib/base/recordHooks.ts:7 \(a refused stale save re-reads the record\). Live help pages, sentences shared: How do I share a vault with a person?; Who can give access, and to whom?; How do I give my AI access to a vault?; How do I connect my AI to GilbApp chat? \(the chat's AI works as you; billed to your own subscription\); How do I connect my computer to my vault? \(acts as its AI vault\); How do I see a record as it was before \(its history\)?; How do I write only if nothing changed \(If-Match\)? \(which GilbApp changes are checked\); How do I continue a project with Kai-Zen?; How do I take access away?.
