Notifications in IcloneU are deliberately simple: there's one place they appear — the bell icon in the top toolbar — and a single bulk control to clear them. This guide walks through what the bell shows you and the events that trigger it. It also sets one honest expectation up front, because the help-center card that brought you here promises more than the product offers today: there are no settings to choose which events notify you, no email or push toggles, and no daily-digest options. The platform — not a setting — decides which notifications you get, and every one of them lands in the bell, though some reach only the account owner's bell; a few important ones are also set up to go to the owner by email. The only alerts you control are the ones you build yourself, with a workflow's Notify Admin step.
Despite the title "Notification preferences" on the help-center card, IcloneU has no preferences surface for notifications. This is the honest "how notifications actually work" guide. If you came looking for per-event toggles or email routing, jump to There are no notification settings (yet) — that section explains exactly where they aren't.
The bell icon and the panel
The bell lives in the top toolbar on every page, next to the search box. When you have unread notifications it carries a red unread-count badge. Clicking the bell opens the Notifications panel.
Find the bell in the top toolbar
Look to the top-right area of any page, near the search box. A red badge with a number means you have that many unread notifications waiting.
Click it to open the Notifications panel
The panel header reads Notifications, with a Dismiss all action at the top right. Entries are grouped under age headers — for example Older for entries from days ago.
Read an entry
Each entry shows an icon, a bold title, a body line naming the object and what happened, a relative timestamp (such as "6d ago"), and — for actionable events — a button that jumps you straight to the relevant surface.
If you ignore the bell, the dashboard's Today's focus card still surfaces the count — it lists "N unread notifications" with an Open shortcut to the same panel. So notifications reach you even without opening the bell.
What triggers a notification
The events seen in this account so far are Knowledge-pipeline events — things that happen as a Knowledge source is processed. The panel is the home for whatever the platform emits, so other event types may appear over time, but these are the ones observed to date:
| Title | What it means | Action button |
|---|---|---|
| Processing complete | A Knowledge source finished indexing — its content is ready for your Clones to use | View Knowledge |
| Discovery complete | A website crawl found pages and is waiting for you to review and select which to add | Review Items |
The action button deep-links to the right place: View Knowledge opens the Knowledge page, and Review Items takes you to the discovered-items review step so you can approve the pages a crawl found. The detailed, per-library log of the same pipeline lives on the Activity sub-tab — a notification is the lightweight cross-surface ping that something there finished.
When a website crawl or sync can't read your site, the bell tells you why. These notices name the collection, say what went wrong and what to try, and carry a View Knowledge button — more in Adding website URLs:
| Title | When it appears |
|---|---|
| Discovery found no items | A crawl looking for your site's pages found nothing to add; the collection's row also shows No sources found |
| We could not check your site | A sync couldn't read the site, so nothing was added, updated or removed, even though Activity lists the run as completed |
| Your website's security certificate needs attention | The site's security certificate was refused (expired, issued for another address, incomplete or not trusted), so the crawl stopped. Ask whoever hosts the site to fix it, then sync again |
Low on units? As the balance approaches zero, IcloneU warns the account owner through this same bell (teammates don't get these warnings), and You're almost out of units is also set up to go to the owner by email — so the owner's bell is also the early-warning channel for the thing most likely to make a Clone fall silent. See Understanding Clone response limits.
Notifications outlive the things they point at
Notification entries are independent of their source objects. Deleting the object does not retract its past notifications — an entry about a Knowledge library stays in the panel, action button and all, even after that library is gone.
Don't be surprised by a notification that points at something that no longer exists. Verified live: a deleted test library's Processing complete and Discovery complete entries were still listed days later, with their action buttons still rendered, while the Knowledge page showed no such library. Clicking such a button simply lands you on a surface where the original item isn't there anymore — it's harmless. Use Dismiss all to clear stale entries.
Clearing notifications
The badge count persists across pages and sessions — it survives navigating around the app and even logging out and back in, rather than clearing the moment you open the panel. You clear notifications deliberately, and there's exactly one bulk control for it:
Open the bell panel
Click the bell in the top toolbar to open Notifications.
Click Dismiss all
The Dismiss all action at the top right clears the list and resets the badge. There's no per-event mute and no way to stop future entries from arriving — but they accumulate quietly as a badge count, with no pop-ups in the app.
Dismissing is about your unread count, not the underlying events. The work a notification reported — a source finishing, a crawl awaiting review — already happened (or is still waiting) regardless of whether you dismiss the ping. For a crawl that's still waiting at Review Items, dismissing the notification doesn't approve the pages; you still need to review them on the Knowledge page.
There are no notification settings (yet)
This is the part the help-center card oversells, so here it is plainly: as of this writing there is no notification-preferences surface anywhere in IcloneU. There are no per-event-type toggles, no settings to send the platform's notifications by email or push, and no daily-digest options. The platform decides what to notify — including the few notices also set up to go to the account owner by email (see the FAQ below) — and you manage them by acting on them or dismissing them. The exception is an alert you build yourself: a workflow's Notify Admin step sends its message as an In-app alert, an Email or both, to the Whole team or Only the automation owner (the account's owner, even when a team member built the automation) — see Workflow actions.
If you went looking, here's where these settings would plausibly live — and don't:
- Account Settings has four sub-tabs — Your details, Billing, Billing preferences and Options — and none of them covers notifications. (Options governs the account's reply behaviour — handover timeout and reply timing — not notifications.)
- The avatar menu (top-right) offers Account settings, Team, Plan and Log out — there's no notifications entry.
- The bell panel itself has no settings or gear icon — just the entry list and Dismiss all.
Treat per-event preferences or email routing as a feature request to raise with your IcloneU contact, not a setting you've failed to find. For now, the levers you do have are: act on a notification via its button, or clear the lot with Dismiss all.
Frequently asked
There's no setting that sends the platform's notifications to email or push, and no digest setting — despite what the help-center card suggests. They all land in the bell icon in the top toolbar. Four of them reach only the account owner's bell and are also set up to go to the owner by email: You're almost out of units, Auto top-up was turned off, Check your AI identifier ✨ (the reminder sent 7 days after you first confirm the AI identifier on a connection) and Customer data request (a customer of your Tiendanube store asked for a report of their personal data). And if the Auto-sync enabled master switch is on, the Weekly auto-sync digest reaches everyone's bell and is set up to go to the owner by email, in any week a sync finished, scheduled or started by hand. For an email of your own, add a Notify Admin step to a workflow with its Email channel on — see Workflow actions. Either way, the bell is the one to rely on. Separately, billing notifications do go to email, but that's invoicing mail driven by the Billing preferences tab, not these event notifications.
There's no mute or per-event toggle. You can't prevent future entries from arriving, but in the app they're unobtrusive — a badge count, never a pop-up. To clear what's there, open the bell panel and click Dismiss all.
There aren't any. Account Settings (Your details / Billing / Billing preferences / Options), the avatar menu (Account settings / Team / Plan / Log out) and the bell panel were each checked — none has a notifications-preferences control. The panel's only action is Dismiss all.
No. Notifications are independent of their source objects, so an entry stays in the panel after the object it referenced is gone, action button and all. It's harmless — clicking it just lands on a surface where the item no longer exists. Dismiss all clears stale entries.
The events seen live so far are Knowledge ones — Processing complete and Discovery complete — and the bell also carries the website warnings and the other notices named earlier on this page. No notification setting switches any of them on or off, so a missing notification isn't a preference you toggled. Two things can still explain one: the notices addressed to the account owner — the low-units warnings, Auto top-up was turned off, Check your AI identifier ✨ and Customer data request — never show in a teammate's bell, and the Weekly auto-sync digest comes only while the Auto-sync enabled master switch is on. The exception is a workflow's Notify Admin alert: it reaches the bell only when its step has In-app alert on. Check the relevant surface directly — for Knowledge, the Activity sub-tab is the authoritative per-library log.
Last updated September 23, 2026 · Account & Settings
