← Your data and vaults while building
Can my app serve several companies or clubs, each with only their own data?
Short answer
Yes: give each company or club its own vault, and share it only with its members; your app shows each person the vaults they reach.
Deeper
What GilbPlatform does today. A vault is the place where a person or a group keeps their records, and each vault has its own access: who may read, write or manage it. A person reaches only their own vault and what others have shared with them, so one club's members do not see another club's vault unless they were given access to it too. So each company or club gets a vault of its own, and each member gets access to their own club's vault only. The answer Can I build for my company, a school, a club or a team? shows how a vault for a group is made and shared.
Who manages each vault. Whoever makes a vault holds Control on it, the level that decides who else may read or write there. A club can make its own vault and share it with its members, or you make it and give the club's admin Control as well, so they let their own members in. 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. The answer Can my app have different kinds of users, such as admins and members? tells which access to give.
What your AI can build. An app can list the vaults the signed-in person can reach, so your AI coder can let a person who belongs to two clubs choose which one they work in. An app can also make a new vault for the signed-in person, who then holds Control on it; a program signed in as itself cannot. Your app gets no more than the signed-in person can, so it cannot show one club's data to another club's members. There is no ready-made screen to manage many clubs at once; your AI coder builds what your app shows.
What to watch. A club's vault can sit inside a vault of yours, but Read or Write given on the vault around it also reaches the vaults inside it, so a person given access there sees every club. Control on the vault around them gives no say over the vaults inside; the answer Does access given to a vault reach the vaults inside it? tells more. An app put live at https://<name>.pages.dev, the address GilbPlatform gives, has no code of its own running on a server today: everything it does runs in the person's browser, with that person's access, so the vaults' access is what keeps the clubs apart.
This answer is written for a computer screen.
Source: Live help pages, sentences shared: Can I build for my company, a school, a club or a team?; Can my app have its own users who sign in? (Your app gets no more than the signed-in person can.); Who can give access, and to whom? (Control); How do I create a vault, list vaults and export one by API? (list the vaults the person can reach; create a vault; a program signed in as itself cannot); Does access given to a vault reach the vaults inside it? (Read or Write on a parent reaches the vaults inside; Control stays). GilbPlatform 0fc5a548 (https://id.gilb.com/version, read 13 November 2026): workers/publish-ingest/src/checks.ts:21 (no server code), :169-171 (what a published app may reach); Standard Rule_Code_deployment (RuleDeployPagesDev).
Checked against GilbApp d529620.