Cheqq Docs
Guides

Manage an App

Create, configure, brand, and publish a Wapp's data and workflows as a public App.

Apps are the public-facing counterpart to a Wapp — see Apps for the audience/binding permission model before configuring one.

Create an App from a Wapp

Open the Wapp you want to publish from, and select Publish as App (or open an existing App from the Apps area).
Choose an audience — Just me, Team, Invited, or Public.
Cheqq opens the App Builder, where you continue configuring and editing pages in chat, the same way you'd build out a Wapp.

Configure bindings

Open the App's Data and Logic settings to control what it can reach:

Under Data bindings, add a collection, choose which operations it allows (read, insert, update, delete), and pick exactly which fields to expose. Leave a field out and the App can never see or write it.
Optionally add a server-enforced filter to a binding so the App only ever sees a subset of rows.
Under Logic bindings, connect a workflow's webhook trigger if the App needs to call it directly.

See Audience and bindings for what each option actually permits.

Set up branded sign-in

For Invited-audience Apps, open Branding to set a headline, subhead, logo, self-signup toggle, and custom CSS for the sign-in screen. Apply your workspace Brand Kit (logo, colors, fonts) so every App you publish starts from a consistent look.

Set the App's search title, description, and social image before publishing so shared links have the intended preview. Published Apps receive a generated *.cheqq.site address.

Connect a custom domain

On a Business-plan workspace, open the App's Domain button:

Enter your domain (e.g. www.example.com).
Add the verification record Cheqq shows you to your DNS provider.
Add the routing CNAME record.
Wait for status to update automatically as DNS propagates — no manual re-check needed.

Rolling out

Custom domains are still finishing rollout — if you don't see the option, check back or confirm your workspace plan.

Your generated *.cheqq.site address keeps working even if you later remove the custom domain.

Preview before publishing

Use the App Builder's preview to check changes before they go live. Previewing your own unpublished App uses a short-lived, App-scoped session that does not affect visitor sessions or make the App public. Publishing invalidates stale dependencies and refreshes the production thumbnail from the deployed App.

Remix an App

Fork a public App you can access as a starting point, then customize it independently. A remix is private and unpublished, does not inherit the source App's domain or visitors, and keeps a reference to the App it came from.

Chat in the App Builder uses the same per-turn checkpoints as other chat surfaces. Restore affects draft source and configuration only—it does not undo an existing deployment, domain, or published visibility. Forking a checkpoint creates an independent unpublished App when the artifact must be duplicated. See History and recovery.

Related: Manage a Wapp for the Wapp this App is published from.

Was this page helpful?