Apps
Publish a Wapp's data and automations as a public site with a default-deny permission model.
An App is a public-facing site built from a Wapp — bound to some of its collections and workflows, deployed to a generated <slug>.cheqq.site address. Where a Wapp is always private to your workspace, an App is how you expose part of it to teammates, invited guests, or the open internet.
Nothing is exposed by default
An App only ever sees what you explicitly connect to it. There's no implicit access to the rest of the Wapp's data — every collection and every workflow an App can touch has to be deliberately bound, and even then, only the fields and operations you allow are reachable. If you haven't bound something, the App can't see or call it, full stop.
Audience
Every App has an audience tier that controls who can open it:
| Audience | Who can access it |
|---|---|
| Just me | Only you, the author |
| Team | Everyone in your workspace |
| Invited | People you specifically invite — they see a branded sign-in screen |
| Public | Anyone, no login required |
See Audience and bindings for how audience interacts with what an App is allowed to do.
Bindings
Two kinds of bindings connect a Wapp's internals to its App:
- Data bindings — bind a collection, choose which operations are allowed (read, insert, update, delete), and pick exactly which fields are exposed. An empty field list means the App can see the collection exists but none of its data.
- Logic bindings — bind a workflow's webhook trigger, so the App's frontend can call it directly.
Full permission model in Audience and bindings.
Build and deploy
Publishing an App compiles a static build of its pages. A deployment moves through draft → building → deployed (or failed, if the build errors). The previous release stays available, so a failed or unwanted deploy can be rolled back instantly. Choose a build target — server-rendered/prerendered pages (better for SEO) or a single-page app — when you set up the App.
Branding and custom domains
Invited and Public Apps can show a branded sign-in screen, and any App can connect a custom domain on top of its generated *.cheqq.site address. See Branded auth and domains.
Where to go next
- Audience and bindings — the permission model in depth
- Branded auth and domains — sign-in screens, sessions, and custom domains
- Manage an App — create, configure, and publish an App