Cheqq Docs
Guides

Notifications

Read what your workflows send you, act on it in place, and control which channels each category reaches you on.

Workflows tell you things: a menu vote closing, an invoice past due, a run that needs your approval, a run that failed. Those messages arrive as notifications — in the bell in the top-right, on the Notifications page, and, depending on the category, by email or push.

Where notifications appear

The bell shows a count of unread notifications and opens a panel of the most recent ones. It is a peek: each body is shortened to a couple of lines so you can scan several at once.

The Notifications page (/notifications, or See all notifications at the bottom of the panel) is the reading surface. Bodies render in full at full width, grouped by day, with an Unread filter and Mark all as read. A workflow that writes a weekly digest or a standings report is worth reading here rather than in the panel.

Reading one

In the panel, a long or formatted body is shortened to a plain-text reading. Select See more to render it properly — headings, lists, tables, and links become live, and links inside the body are clickable. On the Notifications page bodies are already rendered.

Selecting a notification anywhere else on the row opens its destination. Selecting a link inside the body follows that link instead, so the two never fight.

Notifications land where the work is

A notification about a specific record opens that record. One about a collection opens that collection inside its Wapp. The row shows where it leads next to the timestamp.

Acting without leaving

When a workflow pauses on a manual approval step, the notification carries Approve and Decline. Choosing one resumes the run immediately — you do not need to open the run. If the decision cannot be applied (the run already moved on, or someone else answered first), the notification says so and leaves the buttons available to retry.

Repeats from one run

When one workflow run notifies several people, or notifies you more than once, those notifications collapse into a single row marked with how many others it stands for. The event is shown once instead of filling the list.

Push to your desktop

Push notifications reach your browser even when no Cheqq tab is open. Turn on Push for a category in Settings → Notifications — the first time, your browser asks permission to show notifications from Cheqq. Permission is per browser, so a laptop and a desktop each ask once; revoking it in the browser's site settings turns push off for that machine without touching your Cheqq preferences.

Choosing what reaches you

Settings → Notifications controls delivery per category and channel.

The categories are Workflow Alerts, Data Changes, Calendar Reminders, System Updates, Security Alerts, and Integration Alerts. The channels are In-App, Email, and Push. Each category shows its channels as toggles, and the scope selector at the top lets you set this globally or override it for one of your installed Wapps — a Wapp-level setting beats the global one for notifications from that Wapp, and Reset on a Wapp scope returns it to the global defaults.

In-app delivery always happens — a notification is always recorded so you can read it later. The channel switches govern whether it also leaves the app.

Delivery

Each category has one Delivery control: Instant sends every notification as it happens; Daily, Twice Daily, or Weekly batches the category into a digest instead. The individual notifications still appear in-app as they arrive; the digest governs email and push.

Do Not Disturb

Do Not Disturb pauses email and push for 30 minutes, 1, 2, 4, or 8 hours, or until you turn it off. Notifications keep arriving in-app while it is on, so nothing is lost — they just stop interrupting.

Security alerts always get through

Security and integration alerts bypass digests and Do Not Disturb. They are the notifications you would want interrupting you.

Sending your own

Any workflow can send a notification with a Notification step — choose the message, the recipients, and where it should open. Leave the channels unconfigured and delivery follows each recipient's own preferences; pin specific channels only when the workflow genuinely requires them. A notification sent from a Wapp's workflow arrives under that Wapp's name and icon and opens inside it.

Was this page helpful?