# Can my app let people book a time with me, and show my free times?

Checked 2026-11-15 against GilbApp d5296208bbffa2ab70076e6194f5537c4be1ddf7.

GilbPlatform has no booking part, but your AI could build booking into your app with records in vaults, or link to a booking service.

## Deeper

GilbPlatform today. GilbPlatform and GilbApp have no booking or calendar part of their own today, and no help answer shows one.

What an app built on vaults can keep: each booking as a record, with the time, the length, what is booked and who booked it; a record is one piece of data with its own address, such as a person, a place, a thing or a note. A vault is the place where a person or a group keeps their records. A time in a record is kept as a date, or as a moment in UTC, the world's reference time; the developer answer [How do I write values of each kind \(encodings\)?](http://support.gilb.com/help/how-do-i-write-values-of-each-kind-encodings) says more.

Your free times. Your app works out the free times from your opening hours and the bookings already made, and shows them; that is code your AI writes. Stopping two people from taking the same time is code too: see [Can my app stop two people from booking the same time?](http://support.gilb.com/help/can-my-app-stop-two-people-from-booking-the-same-time)

What everyone may see, such as your free times, must be in a vault they may read. "Make public" lets anyone read the vault, so people's names and their bookings belong in a vault that is not public; the answer [How do I make a vault public?](http://support.gilb.com/help/how-do-i-make-a-vault-public) shows how it works. To work in a vault of yours, such as a shared list your app shows everyone, a person needs access you give them, or your app's server reads it for them; the answer [Can my app have its own users who sign in?](http://support.gilb.com/help/can-my-app-have-its-own-users-who-sign-in) says more. A server here is a computer on the internet that runs your app's own code; GilbPlatform does not give your app one. Ask your AI where it keeps each kind of data, and who may read and change it.

You can also use a booking service run by someone else, and link to it from your app. Google Calendar, for example, has appointment schedules: "For eligible Workspace accounts, Calendar automatically generates a booking page", and "Some appointment schedule features require an eligible Google Workspace or Google One subscription" \(https://support.google.com/calendar/answer/10729749, read 13 November 2026\). The bookings are then kept at that service, under its terms, not in your vaults. A published app cannot show that service's page inside its own pages or fetch from it; the security rules for published sites do not block a plain link that opens it. If you need more, write to support@gilb.com.

Tell Kai-Zen, the planning agent, what people may book, how long each time is, your opening hours and who may see what; it changes the plan, and Agent.Coder, the agent that writes your app's code, builds the change. The answer [How does my app handle time zones?](http://support.gilb.com/help/how-does-my-app-handle-time-zones) covers times for people in other places. The answer [Can my app send a reminder before a booking?](http://support.gilb.com/help/can-my-app-send-a-reminder-before-a-booking) covers reminders. The answer [Can a booking also take a payment or a deposit?](http://support.gilb.com/help/can-a-booking-also-take-a-payment-or-a-deposit) covers payment.

This answer is written for a computer screen.

Source: GilbPlatform 0fc5a548 workers/publish-ingest/src/checks.ts:21 and :146 \(functions, \_worker.js, \_headers refused: "a functions folder would run your code on the server"\), :30-37 and :158 \(key-shaped strings, incl. a Stripe secret key, refused\), :165-171 \(the site's own headers: Content-Security-Policy default-src 'self'; script-src 'self'; img-src 'self' data: blob: https://\*.gilb.com; connect-src 'self' https://\*.gilb.com; form-action 'self'; frame-ancestors 'none'\); RuleDeployPagesDev. GilbPlatform 0fc5a548 \(https://id.gilb.com/version, read 13 November 2026\): no booking, calendar, e-mail-sending or timed-job route for apps in src/routes \(e-mail is sent only for sign-in codes, src/auth/send-otc-email.ts, and the owner's monitor alerts\). GilbApp 49b1ae53 \(https://gilb.com/app/version.json, read 13 November 2026\): no booking or calendar control in src. Standards: Proc\_v\_i\_c\_PublishPagesDev \(a built static folder is published at https://&lt;name\>.pages.dev\); Agent.Coder \(GilbStack 14a: a browser-only app cannot keep a key secret\). Live help page, sentences shared: Where do I keep the passwords and keys for the services my app uses? Google Calendar Help, appointment schedules, https://support.google.com/calendar/answer/10729749, read 13 November 2026. Live help pages, sentences shared: Can my app have its own users who sign in? \(access you give, or your app's server\); How do I make a vault public? \("Make public" lets anyone read the vault\); How do I write values of each kind \(encodings\)? \(a date, or a UTC time ending in Z\); What are space and time in GilbVeda \(changing systems\)? \(a delete ends a record and does not erase it\); What does my app need to remember, and how do I tell my AI which information to keep?
