Notifications for Compliance Events

What this means

Breadcrumb creates an in-app notification when a compliance event happens (for example, a document is expiring, an approval step is triggered, or a workflow action completes).
Email and push notifications are optional and depend on each user’s notification preferences and whether that notification type is enabled for the company.
For supplier document expiry specifically, emails are controlled by a mix of workflow configuration, user roles/permissions, and user notification settings.

When you’ll use this

When an admin asks “who gets notified when compliance documents expire?”
When someone says “I’m not receiving compliance notifications”
When you’re setting up supplier document workflows and want expiry reminders to go to the right approvers

Step-by-Step

Understand the 3 delivery channels

In-app notifications: created and shown in the portal/mobile notification list
Email notifications: sent only if enabled for that notification type and the user has opted in
Push notifications: sent only if enabled and the user has opted in

Confirm the notification type is enabled for the company

Notifications can be disabled at a “master toggle” level per company and notification type.
If the master toggle is off, no notification is created at all (so nothing will show in-app, email, or push).

Confirm the user’s personal notification preferences

Even when an in-app notification exists, the user may have email and/or push turned off for that notification type.
Users control this per company and per notification type.

Supplier document expiry emails (most common compliance notification)

Breadcrumb can send two types of supplier document expiry emails:

A) Individual document expiry email

This email lists individual supplier documents that have expired. To receive it, a host user must:

Have an end-user workflow configured for that supplier doc type that includes an approval step
Have a role included in the approval section of that workflow
Have an email address saved on their profile

B) Document expiry summary email

This email summarizes the count of docs that have expired or will expire soon on a site. To receive it:

The expiry summary report must be enabled in Supplier Document Configuration settings
A notification period and workflow kind must be set
The recipient must be a company host or site host with “Has All Permissions”
The user must enable the Supplier Document Expiry (Email) notification in their personal settings
The user must have an email address saved on their profile

Common Issues

“I’m not getting expiry emails”

What to check:

Does the user have an email saved in their profile
Is the correct supplier doc workflow configured (including approval step, where required)
Is the user’s role included in the approval section (for individual expiry emails)
Is the expiry summary report enabled and configured (for summary emails)
Has the user enabled the Supplier Document Expiry email notification in settings

What to do:

Add/update the user email in profile
Fix the workflow approval roles
Enable/configure the expiry summary notification and ensure the user has “Has All Permissions”
Have the user toggle on the relevant email notification in settings

“Why do I see notifications in-app but not by email?”