Org Notification Policy & External Contacts

Organization admins set the notification defaults every member starts from, can switch categories off org-wide, and control the single most consequential switch in the system: whether ClashWise may email external responsible contacts — the people in your clash matrix who don't have ClashWise accounts.

Where to find it

Open Organization at https://clashwise.ai/my/organization and find the NOTIFICATIONS card (admins only; members see the settings read-only).

The org master switch

Clash notifications on/off for the entire organization. Off silences everything for everyone — email and in-app — including external contacts. Use it as the emergency brake; for day-to-day tuning use the category and member-level controls instead.

Category defaults and hard-disabling

For each category (assignments, due dates, activity on sets, sessions) the organization sets the default cadence members inherit until they pick their own. An admin can also hard-disable a category: it goes dark org-wide and members cannot re-enable it — their profile shows it greyed with a note.

Out of the box (no admin changes): assignments are immediate, due dates and set activity are daily digests, sessions are immediate.

Due-soon lead time

Due-soon lead time sets how many days before a clash's due date the due-soon notification fires (default 3). Pick the horizon that matches your coordination rhythm — weekly cycles often prefer 5–7 days.

Emailing external responsible contacts

Matrix contacts are real people — named, with email addresses — but usually not ClashWise users. When this switch is on, they are emailed about clashes assigned to them and their due dates, at the cadence you choose here (they hold no preferences of their own; daily digest is the default and a sensible one).

This switch is off by default. Emailing third parties is an explicit decision your organization makes — nothing external is sent until an admin turns it on.

What external contacts receive

Links are valid for 30 days and refresh every time a new notification email goes out, so an actively-notified contact always holds a working link.

Controlling external access

If a contact is also a member

A matrix contact whose email matches an active member of your organization is treated as that member: their own preferences apply, notifications reach their in-app feed, and they get normal app links — never the external read-only view. The external switch is irrelevant for them.

Tips

FAQs

Will external contacts be emailed the moment we assign them in a matrix? Only if the external switch is on. It's off by default — assignment stays an internal fact until your organization opts in.

Can an external contact see clashes that aren't theirs? No. The read-only view is scoped to the clashes where they are the responsible contact, in that one set.

Can external contacts reply or edit? No. The page is read-only and the email comes from a no-reply address. To collaborate interactively, invite them to your organization.

Who counts as the set owner? The user who published the set from Navisworks. Ownership drives who receives activity and due-date notifications for the set.

Troubleshooting

Limitations

Related topics

Start free trial Download plug-in See pricing