Notifications keep work moving through the platform by alerting the person responsible for the next step. They are generated across Actions, Action Plans, skill builds, observations, certifications, and comments.
In this article, you will learn:
How Notifications Are Delivered
Notifications are delivered through two channels:
Notification Center - available in both the web portal and the mobile application.
Email - mirrors the Notification Center one-to-one. If a notification appears in the Notification Center, a corresponding email is sent.
Each notification generates its own individual email. Notifications are not batched or grouped into a single message per user.
Notification Center web portal and the mobile application
Email
Enabling email does not backfill. When email delivery is switched on, emails are sent only for notifications generated from that point forward. Existing unread or overdue items do not trigger a retroactive send. Email delivery is currently an organization-wide setting. It cannot be enabled for individual components, user groups, or notification types. Every notification email contains a Review button that opens the relevant item directly in the application rather than the home page.
Who Receives a Notification
Notifications are sent to the person responsible for completing the next step, not to the associate who is the subject of the work.
For example, when an observation is assigned, the observer is notified because the observer must perform the observation. The associate being observed is not notified.
Where a workflow has multiple participants, notifications follow the sequence of responsibility, moving to each participant as their step becomes active.
Actions and Action Plans
Notifications are generated for both standalone Actions and Action Plans.
Every Action type generates a notification. The Action types available depend on where the Action is created:
Entry point | Behavior |
Associate profile | Observations, skill builds, and certifications are assigned through their dedicated Assign/Add paths rather than as Action types. |
Navigator | Certify, Observe, and Skill-build are available as Action types, so any follow-through can be initiated from a single location. |
Associate profile
Navigator - Actions
The entry point changes how the work is created, not who is notified. The resulting notification is the same either way.
Action Types and Notification Recipients
Each Action type generates a notification when it is assigned. The recipient is the person who must carry out the work.
Action type | Available from | Intent | Notified on assignment |
Certify | Navigator only | Assign and complete a certification, or re-certification, for an associate on equipment or a specific job function. | Assigned Trainer |
Coach | Associate profile, Navigator | Conduct a 1:1 follow-up conversation to provide feedback, clarify expectations, and reinforce correct behaviors. Used when awareness, alignment, or judgment is the gap — not skill. | Assignee |
Engage | Associate profile, Navigator | Initiate a purposeful check-in to understand context, surface concerns, or rebuild alignment when signals are ambiguous. Used to gather insight before choosing a more prescriptive action. | Assignee |
Investigate | Associate profile, Navigator | Analyze a systemic issue, trend, or recurring signal to determine root cause and appropriate intervention. Used when the problem is not isolated to a single person. | Assignee |
Observe | Navigator only | Assign a targeted observation to assess how work is being performed against the standard. Used to validate behavior, identify gaps, or confirm improvement. | Assigned observer |
Skill-build | Navigator only | Assign structured skill-building to develop capability in a defined job function. Used when the associate needs guided practice or progression — not remediation. | Assigned skill builder, then the associate |
Validate Fix | Associate profile, Navigator | Confirm that a completed action or change has resolved the original issue and that performance or behavior has stabilized. Used to close the loop and prevent regression. | Assignee |
Observation Notification Flow
1. A leader creates an Observe Action for an associate and assigns an observer.
2. The observer receives a notification indicating that they need to observe the associate.
3. The observer logs in to the application and navigates to the Actions section.
4. The assigned observation appears in the Actions list, and the observation can be started directly from there.
Action from Navigator
Web Portal inbox
Notification from App
Email Notification
Skill Build Notification Flow
When a skill build is configured as self-guided, the associate works through the checklist independently. No skill builder has to run the training first, so the first notification goes straight to the Manager to assign it to the associate.
A Manager assigns a self-guided skill build to an associate.
The associate receives a notification prompting them to complete the skill build.
The associate opens the skill build, works through each checklist item, and marks each one complete. When every item is checked off, the Sign Off button appears.
The associate signs off.
What happens next depends on the sign-off flow configured on the skill build:
Associate sign-off only: the skill build moves directly to Completed. No further notifications are generated.
Trainer sign-off required: the trainer receives a notification that the build is ready for review. The trainer validates the completed items and performs the final sign-off, and the skill build moves to Completed.
In a self-guided build, the associate always signs off first. The trainer can't perform the final sign-off until the associate has done so.
Component | Condition | Recipient | Methods |
Skill-build Action (self-guided) | Manager Assigns | Associate | Notification Center, Email |
Skill-build Action (Trainer-led) | Manager assigns, Associate signs off, trainer sign-off required | Trainer | Notification Center, Email |
Action from Navigator
Web Portal inbox
Notification from App
Email Notification
Notification Reference Table
Component | Condition | Recipient | Methods |
Certify Action | Assigned | Assigned Trainer | Notification Center, Email |
Coach Action | Assigned | Assignee | Notification Center, Email |
Engage Action | Assigned | Assignee | Notification Center, Email |
Investigate Action | Assigned | Assignee | Notification Center, Email |
Observe Action | Assigned | Assigned observer | Notification Center, Email |
Skill-build Action | Skill builder assigned | Assigned skill builder | Notification Center, Email |
Skill-build Action | Ready for associate to complete | Associate | Notification Center, Email |
Skill-build Action | Ready for sign-off | Next sign-off in flow | Notification Center, Email |
Validate Fix Action | Assigned | Assignee | Notification Center, Email |
All Action types | Overdue | Assignee | Notification Center, Email |
Skill builds | Overdue | Trainer on record | Notification Center, Email |
Certifications | Expiring, expired, revoked | Trainer and Leader | Notification Center, Email |
Comments | User tagged in a comment | Tagged user | Notification Center, Email |
Content Manager Notifications
Content Collaboration generates a separate stream of notifications for anyone working in Content Management (Articles, Stories, Job Functions, Checklists, and other content types) — distinct from the Action, skill build, and observation notifications above.
A content manager is notified when:
A piece of content is assigned to them.
They are tagged in a comment on a piece of content.
A comment is added to a piece of content they are the Creator of, are Assigned to, or are Tagged on.
For the full collaboration workflow — commenting, tagging, assigning, and changing status see the Content Collaboration article.
Publishing & Notifying End Users
Separately from the collaboration notifications above, end users (associates, leaders, and other content consumers) are notified when new content is published or when an existing piece of content is updated.
This applies to Articles, Job Functions, Stories, and other published content types. Tapping the notification takes the end user directly to the new or changed content; multiple updates can be paged through from the same notification view.
Daily Digest & Report Subscriptions
The notification emails described throughout this article are separate from report subscriptions. Each notification generates its own individual, real-time email as soon as it is created; it is not held, bundled, or summarized into a digest.
Subscriptions are a distinct feature that automate reporting delivery, keeping you informed without manual effort. When subscribing to a report, leaders receive it by email on the schedule set to daily, weekly, or monthly.
