Manage a Wapp

Install, open, create, publish, and manage focused AI-powered solutions in Cheqq.

Open a Wapp

Select Wapps in the main navigation to see every Wapp you have. Each one says what it has been doing — "3 changed this week · 20 records", or "5 records · last change 16 Sep" after a quiet week — so you can tell at a glance which ones are in use.

A Wapp opens on its first dashboard: what it is tracking comes before where it keeps it. A Wapp with no dashboards opens on its first collection. A link to a specific collection or record still opens exactly there. A business system opens on Home instead, while its Getting started list is showing.

Chat inside a Wapp is scoped to that Wapp. Before you've said anything, it suggests up to three things to ask — led by whatever needs you, such as a failed automation or unfinished setup.

Home

Every Wapp's first tab is Home. It gathers the Wapp's Getting started list, when it has one, cards for its records, its automations and the people with access, the Apps built from it, and its documents.

Move around a Wapp

The Wapp's sidebar lists its dashboards first, then its collections. A collection reopens on the view you last used there.

Back and Forward move through the collections, dashboards, views, and records you opened, the way they would on any website. Back closes an open record; Forward opens it again. Stepping through records with the record panel's arrows doesn't add a step for each one.
⌘K (Ctrl+K on Windows and Linux) opens a palette that goes to any dashboard, collection, or view in the Wapp.

Ask about what you're looking at

The Wapp's chat invites you to ask about the collection on screen, and its first suggestions include a question about it. With a record open, select Ask about this record to start a new conversation with that record already named.

On a phone

A Wapp's dashboards and collections sit in a strip across the top — dashboards first — so you can see everything it holds and switch with a tap. The strip scrolls sideways, and the button at its end counts what's out of sight and opens the full list.

Adding a record is a floating button in the bottom corner. A bar along the bottom — Ask about followed by the page you're on — opens the chat with that page already written in. Home, members, settings, and the Skills, Workflows, and Instructions sections are in the header's More menu. See Cheqq on your phone for the rest of the phone layout.

Finish setting up an installed Wapp

A Wapp you installed from the store can arrive with work left to do — a service to connect, a device to pair, or an automation to switch on. Those are listed as setup steps, reachable from the badge on the Wapp and from its setup page. A business system walks you through the same things in its Getting started list on Home, and the Finish setup badge stays out of the way while that list is showing.

Automations install switched off on purpose

Every event-triggered workflow a Wapp provisions arrives off, so a fresh install can't act on its own sample data before you've read what it does. A setup step says so for each one — whether it's simply waiting for a switch, or needs something only you have, like an endpoint or a key.

None of these can block an install: a Wapp that ships an automation switched off is saying it works without it. Turn them on when you're ready, from the Wapp's Workflows section.

Stop reminding me about these is remembered per step, so a workspace stops counting something you deliberately passed on. A later update that ships another switched-off automation can still raise its hand, because that's something you haven't seen yet. Dismissing only drops the prompt — the automation itself stays in place, ready whenever you want it.

A Wapp that installed with sample records shows a Sample data card on the same page, and a business system's Home offers the same while they remain. Clear sample data asks first, then removes the sample records. It keeps any sample record you've edited, anything you or a workflow has added since, and the setup records a template starts you with, such as its settings.

Create a Wapp

Select New Wapp on the Wapps page, or Create new Wapp beside the installed Wapps in the sidebar.

Enter a Wapp name — a slug preview appears below it, and the slug can't be changed later.

Add an optional description of what the Wapp should do.

Select Create Wapp. You land in the new Wapp's workspace and continue refining it in chat.

Test the generated experience and data behavior before relying on it or adding sensitive data.

A collection you add by hand starts with one blank record, the way a new spreadsheet starts with a row to type into. One undo removes both.

Wapp settings

Open Settings from the Wapp header. If you created the Wapp — or installed it, which makes the copy yours — Settings covers:

General — name, read-only slug, description, and icon: an emoji or a 74-icon catalog with search.
Appearance — the accent color and card pattern. Every Wapp starts with a generated identity derived from its name; pick your own or shuffle for a new one.
Browser Access — which domains and actions the Wapp's agent may reach in Companion extension sessions, whether it persists its session, and whether it requires you to be logged in.
Template — share the Wapp as a link anyone can copy into their own account. See Share and remix.
Lifecycle — Archive/Restore, Duplicate, and Delete.

Changes to General fields save automatically as you edit them.

Teammates who use a Wapp you shared with the workspace see its setup page instead: setup steps, version, and sample data.

Wapp lifecycle actions

Archive — makes the Wapp read-only; Restore reverses it.
Duplicate — creates an independent copy you can change without touching the original.
Delete — the one way to remove a Wapp. Only the person who created or installed it can delete it.

Delete and restore

Delete asks first, and says how many teammates lose the Wapp too and that its live Apps go offline. The Wapp moves to the Trash drawer on the Wapps page, where you can restore it for 7 days (30 on paid plans). You can also ask the Wapp's chat to delete it; it asks you to confirm the same way.

While a Wapp is in Trash, its inbox addresses stop receiving mail and no longer count against your plan. Restoring it brings back everything:

Records and collections, as they were.
Automations, running if they were running before — triggers and schedules included. One that depends on something that has since gone stays paused.
Apps, ready to publish again. They stay offline until you publish them.
Inbox addresses, receiving mail again. If you deleted an address yourself while the Wapp was in Trash, the restored Wapp gets a new one — give the new address to anyone who forwards mail to the old one.

Restoring needs the same room in your plan as installing the Wapp would. If there isn't enough, Cheqq says so before changing anything.

An automation still using it

If one of your other automations calls the Wapp, Delete names it and offers to move it to Trash with the Wapp: Delete with workflow. You can restore each one from Trash on its own. Automations made for the Wapp itself always go to Trash with it.

After its time in Trash, or when you select Delete permanently, the Wapp is removed for good with its records, automations, and addresses.

Update a Wapp you installed from the store

Installing a store template gives you your own copy, so improvements published to the template afterwards don't reach you until you take them. When a newer version is available Cheqq tells you three ways: a dot beside the Wapp in the sidebar, a card at the top of its settings page, and a notification.

Open the Wapp and select Settings.

Read the Update available card. It names the version you're on and the one being offered, and lists what taking it will do: changes to how your records are stored, new collections, fields and views, workflows that improve, arrive or retire, new documents and Apps, anything that keeps your version, and connections the new version needs.

Select Update to x.y.z. Cheqq applies the new version and tells you what it changed.

What an update keeps

An update is additive wherever it can be. It keeps:

Your records. Nothing is deleted. If the new version changes how a field is stored — renaming it, or switching a "Minutes" number to a Duration — your existing values are converted, and the update card tells you so before you agree to it.
Fields you added yourself. A field you created stays, with its data. If the new version happens to introduce a field of the same name, yours is kept alongside it under a numbered name rather than being replaced.
Your views. Filters, sorts, visible columns and widths survive. New settings the template introduces are filled in only where you hadn't chosen one yourself, and views the new version adds are created alongside yours without changing which view opens by default.
Your Wapp's identity. The name, icon, colour and description you set stay yours — an update never resets them to the template's.
Workflows you've changed. A workflow whose steps or triggers you changed — a different schedule or timezone, a filter, a step of your own, or the inputs it asks for — keeps your version exactly. The card lists it under Kept as yours before you update. A workflow the new version retires stays too if you changed it, as your own. When Cheqq has no record of the version you were on, it can't tell a workflow you changed from one that is simply older, so it keeps those as they are and says it couldn't tell; you can take the new version of any of them yourself.
Your Apps and documents. An update adds the Apps and documents the new version brings, and never changes or replaces one you already have. A form or portal that starts one of the Wapp's automations keeps starting it, and an App you deleted stays deleted.
Your automation decisions. Whether each workflow is switched on, the Mailhook address people already forward mail to, and the endpoint an App sends to stay as you left them. Workflows you wrote yourself are never touched.

What it replaces:

Workflows you haven't changed take the new version's steps and trigger settings in place, keeping their run history. If you renamed one, it keeps your name.
Workflows the new version retires are removed, if you hadn't changed them.

New collections, fields and automations from the template are added; new automations arrive switched off. When the new version fixes how a formula or a rollup counts, your existing records are recalculated too, not only new ones.

Take the template's version of a workflow you changed

After an update, a workflow that kept your version shows Your version differs from the template's at the top of the Wapp's Workflows tab. Select Use the new version to replace its steps and triggers with the template's. It stays switched on or off as it was, keeps its inbox and App connections, and keeps its name. The change is in the workflow's version history, so you can go back. Owners and admins of the Wapp can do this, when they may change that workflow's steps; you only see the workflows you can open, and a count of any others that differ.

Update an App or document you haven't changed

Cheqq remembers what a template wrote into each App and document it made. When the template has a newer version of one that nobody has changed since, the Wapp's Home shows it under Newer versions from the template, with Update beside it.

An App gets the new version in its draft, and its preview rebuilds. If it is live, visitors keep seeing the published version until you publish again, so an update never takes a live App down. The App Builder keeps a checkpoint from before the update, so you can go back; without one the update doesn't start, and an App someone edited in the meantime is left as it is. Any file you added to an App, wherever it is in its source, counts as a change.
A document gets the new version as a new version in its history, where the earlier one stays. Its title, and any rename you made, stay as you have them. A document with edits that haven't been saved yet is left alone until you save or discard them.
One you've changed keeps your version and is never offered an update.
Apps and documents made before Cheqq kept track of this aren't offered one either, since Cheqq can't tell whether they were changed.

Only the person who installed the Wapp can update its Apps and documents.

A new version may ask for a new connection

If the incoming version needs an integration you haven't connected, the Wapp moves back to setup until you connect it. Everything already in the Wapp stays where it is.

Publish a Wapp as an App

A Wapp's collections and workflows can be bound to a separate public site — an App — deployed to a generated *.cheqq.site address, with its own audience and permission model. See Apps for how that works and Manage an App for creating, binding, branding, and publishing one.

A business system arrives with its Apps already built, ready for you to publish from its Home. See Apps that come with a template.

Undo and redo

Open History from the Wapp header to browse the shared timeline. Every supported committed change—from a person, agent tool, import, chat restore, or other recorded source—becomes an immutable entry.

Undo and Redo move the collaborative history cursor. Keyboard shortcuts work outside editable text fields.
Compare explains structural changes and semantic record differences, including records or fields that were added, changed, deleted, or restored.
Restore creates a new, undoable entry from an older version instead of rewriting the timeline.
Name snapshot pins an existing entry on paid plans. Free workspaces can use ordinary retained history and see the upgrade option when naming.
Trash recovers deleted Wapps (from the Wapps page), collections, and records.

Wapp history includes its settings, structure, views, dashboards, owned instructions and skills, workflow links, and collection records. It does not reverse external effects or alter standalone workflow definitions. Read History and recovery for retention and exact coverage.

Open the Wapp's Workflows section to see the automations scoped to it, or use the Workflows guide for the editor and run controls.