Sharing & visibility

Every page can be private, shared with named people, company-wide, or fully public.

Default when you don't choose: a work-email account publishes company-visible (anyone signed in at your domain); a personal account publishes public (after a one-time content-policy consent).

Override it per page in the dashboard, or with a flag on the CLI:

ModeWho can view
--privateOnly you.
--invites a@co.com,b@co.comYou and the people you list (they sign in to prove it). No Drive needed.
--workspaceAnyone signed in at your company domain. default · work accounts
--publicAnyone with the link, after a one-time content-policy consent. default · personal accounts

Preview, then promote

When an AI assistant publishes for you (via the Quickish connector), the new app lands as a private preview — only you can see it while you iterate, real backend and all. When it's ready, open the dashboard and hit Promote on the page card to make it live in one click (company-visible for work accounts, public for personal — same one-time consent as above).

Promoting only flips who can view it — the page and its data carry over untouched, because the preview is the page. Publishing from the CLI is direct: it uses the visibility you pass (or the account default), no preview step.

Remix an app

See a Quickish app you like? Remix it into your own copy. In the dashboard, paste the app's URL and hit Remix — you get a brand-new private preview under your account (with its own fresh backend) to edit and then promote.

Remixing is opt-in: an app can be remixed only if its owner turned on Remixable for it (off by default), and then only if it's public or shared inside your own company. To let people remix one of your pages, flip the Remixable toggle on its card in the dashboard (or publish with --remixable). A remix starts with an empty database — it never copies the original's live data — unless the source app marks a collection as sample data, in which case those example records come along so your copy isn't blank on first run.