MyJackfruit

Help
Browse topics · Finishing

Finishing

← Finishing

Can someone else on my team put my app live?

Short answer

Only the account that holds the site's name can publish it. A teammate can build with you, but the name's holder publishes.

Deeper

Who holds a site. A site belongs to the person whose account first took its name, also when their AI published it for them. Only that account can publish it again. If a teammate, signed in with their own account, publishes under the same name, it is refused with The site name '<name>' is already taken. Choose another. Nothing is put live, and your site stays as it is.

Two people cannot both publish the same site. GilbPlatform has no way to add a second person to a site, and no way to hand a site over to another account. If you need this, write to [email protected]. Sharing the project's vault with a teammate, even giving them Control of it, does not let them publish your site: the account that holds the name still does.

A teammate's own name is a new site. If a teammate publishes the app under another name, it is a second site, at another address, and uses one of their own 2 sites. Your users would then have two addresses for one app.

Building as a team. Several people can build the same app. The project is kept in a vault you share, and each person signs in with their own account and can use their own AI, on their own subscription. Their code comes together through a shared store for code, such as GitHub, a website where programmers keep and share code. The answer Can two people's AIs build at the same time without getting in each other's way? shows how, and Who owns a project when several people work on it? tells who holds the project. When the work is ready, the person who holds the name says yes to going live, and their AI publishes it. Your AI is told never to put your app live without your yes.

From another computer. For an app, the connector, the small GilbPlatform program on your computer, keeps a key on the computer the app was published from; the platform lets the app sign people in with that key. Published again from another computer, the app gets a new key there, which takes the old key's place. If you can, publish updates from the same computer.

This answer is written for a computer screen.

Source: GilbPlatform 0fc5a548 (https://id.gilb.com/version, read 13 November 2026): src/publish/records.ts:386-391 (another person's claim: is already taken. Choose another.), :423, :479 (one owner per site, written at claim and at publish), :256 (2 sites per person); src/routes/publish.ts:390 (This site name is not held by this account.), :4-9 (a Connected AI's ticket names the person it acts for); src/publish/admission.ts:8-9 (a re-publish with a different key replaces the old one's approval); no route or script that adds a publisher or moves a site (src/routes/publish.ts:278, :413, :442 are the only publish routes). Standards read from GilbPlatform on 13 November 2026: Standard Rule_Code_deployment (RuleDeployPagesDev: a site always belongs to a person; a Connected AI publishes for the person it acts for), Agent.Coder (AskGoLive: never publish without the person's yes). Live help pages, sentences shared: Can two people's AIs build at the same time without getting in each other's way?; Who owns a project when several people work on it?; How do I update my app after it is live? (another computer).

Checked against GilbApp d529620.