Can my app have different kinds of users, such as admins and members?
Short answer
Yes, through access to a shared vault: admins get Control as well, members Write + Read or Read; your AI builds each one's screens.
Deeper
GilbPlatform, the service that keeps your vaults, has no list of admins and members for an app. What it has is access: who may read, write or manage each vault and each record. A vault is the place where a person or a group keeps their records; a record is one piece of data with its own address. Kinds of users are built from that access.
What GilbPlatform does today. An app on GilbPlatform does not keep its own users: each person signs in with GilbPlatform and has their own vault. Data that several people use together, such as a club's list of events, is kept in a vault made for it, a shared vault. Whoever holds Control on a vault decides who else may read or write there; you hold it on a vault you made. In GilbApp you give each person one of four levels. Read lets the person read the vault. Write + Read lets them read it and also write to it. Append lets them add to the vault only, not read or change what is there. Control lets them manage who else has access. 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. Access can also be given on one record only. The answer How do I share a vault with a person? shows the steps.
So a member can have Write + Read or Read on the shared vault, and an admin Write + Read and Control as well, so that the admin can let new members in and take access away. Holding Read, Write or Append lets a person give access to no one. In GilbApp, the people who hold Control on a vault see who has access to it under OTHER PEOPLE AND GROUPS ACCESS RIGHTS; the answer How do I see who can reach my vault? shows it.
What your AI can build. An app can ask GilbPlatform what the signed-in person may do with one record: read, write or control. GilbPlatform answers only about the person asking, never about someone else. So your AI coder can make your app show admin screens, such as adding or removing members, only to the people who hold Control, and member screens to the others. Tell your AI which kinds of users your app needs, and what each kind may see and do.
What it does not do. Showing or hiding a screen does not protect the data. What a person may read or write is decided by GilbPlatform, from the access they were given, not by your app's screens: your app gets no more than the signed-in person can. So give each person only the access their kind needs. 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 access you give each person is what keeps the kinds apart.
GilbPlatform has only these four levels, given on a vault or on one record; a name such as editor or treasurer is your app's own word for one of them. GilbPlatform can also give access to a group, several people given access together, or to one record and everything part of it, or to only one type of record there. GilbApp has no screen for a group, for everything part of a record, or for one type; for one record on its own it has one, as the answer How do I share one record (not the whole vault)? shows. The developer answer How do grant scopes work (cascade, type, preview)? tells more.
An example that works today: in MyNet, Gilb's app for your profile and network, a group has members and admins. Its admins answer requests to join, and Accept gives the new member Read on the group's vault. The answer How do I see a group's members? tells more.
This answer is written for a computer screen.
Source: Live help pages, sentences shared: How do I share a vault with a person? (the four access levels: Read, Write + Read, Append, Control); Who can give access, and to whom? (Control decides; Read, Write or Append give access to no one; groups; GilbApp offers Person and Vault); Can my app have its own users who sign in? (Your app gets no more than the signed-in person can.); How do I see who can reach my vault? (OTHER PEOPLE AND GROUPS ACCESS RIGHTS; an app can ask what the person may do with one record); How do grant scopes work (cascade, type, preview)? (GilbApp has no screen for these grants); How do I see a group's members?; How do I find and join a group? (Accept gives Read). Developer Guide Dev.Guide.Overview (WhatItIs, NoKeys), read 13 November 2026. GilbPlatform 0fc5a548 (https://id.gilb.com/version, read 13 November 2026): workers/publish-ingest/src/checks.ts:21 (no server code), :30-37 (key-shaped strings refused), :124-140 (file limits), :169-171 (what a published app may load and reach). Standard Rule_Code_deployment (RuleDeployPagesDev).
Checked against GilbApp d529620.