Introduction to Notifications

ClashWise keeps everyone on a coordination effort informed automatically: responsible contacts hear about clashes assigned to them and coming due, and clash-set owners hear about activity on the sets they published — by email, in the web app's notification bell, or both. You control how much you hear and how often, from a single stream of events.

Why you'd use it

Clash coordination fails quietly: a contact never learns a clash was assigned to them, a due date slips past unnoticed, an owner doesn't see that a teammate re-triaged half their set. Notifications close those gaps without anyone having to remember to check — and digests keep it from turning into inbox noise.

What triggers a notification

Four kinds of events generate notifications:

Assignments — a responsible contact is set on a clash (by a person, a matrix rule, a bulk edit, or a matrix analysis run). The assigned contact is notified; bulk operations arrive as one grouped notification ("12 clashes assigned to you"), never one per clash.
Due dates — a clash is due soon (a configurable number of days ahead — 3 by default, set by your organization), due today, or overdue. The responsible contact and the set owner are notified. Overdue reminders repeat weekly — not daily — while the clash stays open, and stop entirely once the clash's Navisworks status is Resolved or Approved.
Activity on your sets — someone else changes a clash's status, priority, contact, due date, or title on a set you published. Owners see what changed, from what to what, and who did it (including edits made through Wise).
Coordination sessions — a session starts or ends on one of your sets, and when the AI minutes are ready.

You are never notified about your own edits.

Where notifications arrive

The bell — the notification icon in the web app's top bar shows an unread badge and a flyout of your latest items. Clicking an item marks it read and jumps to the clash (always identified by its permanent #N number). The full feed lives at https://clashwise.ai/my/notifications, with paging and an unread-only filter.
Email — sent through the same stream, on the schedule you choose (see below). Every email deep-links back to the clash set, and external responsible contacts receive a secure read-only link instead (see the organization policy article in this section).

Immediate or digest — you choose the rhythm

Each notification category has an email cadence:

Immediate — one email per event, sent within minutes.
Hourly digest — everything from the hour, grouped into one email.
Daily digest — one email around 08:00 in your local time zone (set your time zone in your profile).
Weekly digest — one email on Monday morning, local time.
No email — in-app only.

Digests group items by clash set so a busy day reads as a scannable summary, capped to keep emails a sane length with an "and N more" link into the app. A daily safety cap also applies: if a single day would generate an unusual number of individual emails, the overflow folds into your daily digest instead of flooding your inbox.

Sensible defaults apply out of the box — assignments arrive immediately, due-date and set-activity notifications arrive as a daily digest — and both your organization and you can change them (see Notification Preferences and Muting in this section).

Who receives what

Event	Assigned contact	Set owner
Assignment	✔	— (unless someone else made the change)
Due soon / due today / overdue	✔	✔
Activity on the set	—	✔
Session started / ended / minutes	—	✔

A responsible contact who is also a member of your organization is treated as a signed-in user — their own preferences and in-app feed apply. Contacts without a ClashWise account can receive email only, and only when your organization has explicitly turned external contact emails on.

Tips

Leave assignments on immediate and everything else on a daily digest — you'll hear about new work right away without a noisy inbox.
The bell updates live while you're in the app — you don't need email at all if you work in ClashWise daily.
Clearing a clash's due date, or resolving it in Navisworks, stops its due-date reminders.

FAQs

Do notifications cost AI actions? No. Notifications are part of the platform. (Asking Wise to send a custom email is different — see Notifications with Wise.)

Why did a bulk edit only produce one notification? By design. Bulk operations, analysis runs, and re-publishes are grouped into a single notification with a count, so a 500-clash operation never sends 500 emails.

I edited my own clash — why no notification? Your own actions never notify you; notifications exist to tell you what others did, and what's coming due.