Skip to main content

Search

Pinnacle Series Admin Features

Admin features for Pinnacle Series.

EP background

Pinnacle Series Notifications - Overview Guide

Applies To:

  • Users
  • Admins
     

Common Causes/Issues:

An overview of Pinnacle Series notifications.

 

Solution Overview:

A complete overview of all notification types across Pinnacle Series, including Learning, Content, Libraries, SPARK, and system behaviours.

 

Executive Summary

Pinnacle Series notifications form the backbone of real-time user awareness. This guide distinguishes clearly between the Admin Journey - where notifications are configured, triggered, and managed - and the User Journey - where notifications are received, acted upon, or dismissed. Understanding both perspectives ensures clarity, reduces confusion, and strengthens adoption.

The Admin Journey

  • Configures global email notification settings
  • Creates and sends manual content notifications
  • Manages Library distribution & Library notifications
  • Controls SPARK activation and rules
  • Monitors assignment reminders & due date logic
  • Responds to notification-related support queries

The User Journey

  • Receives in‑app notifications in Peak Experience
  • Optionally receives email notifications (if enabled)
  • Acts on Learning Path deadlines & reminders
  • Responds to SPARK insights & nudges
  • Views Library‑related updates when new content is shared
  • Can disable their own email notifications to opt‑out

 

Core Notification Logic (at a Glance)

To avoid overwhelming you with technical depth up front, here are the four principles every admin and user should know. Each one is explained in detail later in the guide.

  1. Two Toggles Control Everything: Admins control global email notifications. Users can override email delivery for themselves under user profile settings, providing the global email setting is enabled.
  2. In-App First: Bell notifications appear in-app first. The global email setting only applies to these bell notifications—email is used only if allowed and the notification is still unread.
  3. 5-Minute Check: The system reviews unread bell notifications every ~5 minutes to determine whether a “missed notification” email should be sent.
  4. Read = No Email: If the user reads an in-app notification before the batch sends, no email is triggered.

User-Facing Notifications

  • Learning Path Alerts
  • Content Notifications
  • Library Updates
  • SPARK Nudges

System Notifications

  • Auto-Transcription
  • Library Status Events
  • SPARK Signals
  • Assignment Logic

Admin Responsibilities

  • Global Email Settings
  • Content Notifications
  • Library Distribution
  • SPARK Configuration

 

1) Admin vs. User Notification Settings
 

Understanding the Two Toggles

Notification delivery in Pinnacle Series is governed by two separate toggles—one controlled by the Admin, and one controlled by the User. Both must be understood together to predict whether an email will actually send.

 

Admin Email Notification Toggle

  • Controls whether unseen in-app notifications are automatically sent to users via email.
  • When enabled, any in-app notification that is not viewed within ~5 minutes is sent to the user as an email.
  • When disabled, users will still receive in-app notifications, but missed notifications will not be emailed.
  • This setting does not affect emails that administrators explicitly choose to send from other areas of the platform (e.g., Assignments, SPARK, Users).

 

Important clarification:

  • Admin-initiated emails from Spark, Assignments, and User management are not governed by this toggle.
  • If an admin enables email delivery within those features, emails will be sent regardless of this setting.

  • This setting applies only to the automatic email delivery of missed in-app notifications.

     

 

View Notifications Overview

User Email Notification Toggle

Note: This toggle is only visible when the Admin global email setting is enabled.

  • Controls whether missed in-app notifications are sent to this user via email.
  • When enabled, the user will receive an email if an in-app notification is not viewed within the system’s delivery window.
  • When disabled, the user will receive in-app notifications only.
  • This setting applies only to the automatic email delivery of missed in-app notifications.
  • It does not affect emails explicitly sent by admins from Spark, Assignments, or User management.
  • It cannot override the Admin-level email notification setting.

 

 

How the Toggles Work Together

Admin Toggle User Toggle Email Sent?
ON ON YES (if notification stays unread)
ON OFF NO (user opted out)
OFF Not visible (Admin toggle is OFF) NO (global email disabled by admin)

 

Key Rules to Remember

  • Email is never sent if the user has disabled email notifications—even if the admin toggle is enabled.
  • Email is never sent if the admin toggle is disabled—regardless of the user toggle.
  • Email is only sent when both toggles are ON and the notification remains unread during the 5‑minute batch check.
  • In‑app notifications are always delivered, even if email is turned off.

 

2) Learning Path & Course Notifications

 

Learner Triggers (User-Facing)

  • A new Course or Learning Path is assigned (in-app + optional email)
  • A due date is approaching (reminder)
  • An item becomes past due (alert)

 

Important: Personalized Training Notifications

When a user self-enrolls in an assessment and selects mapped training to automatically assign personalized training, the platform does not send an email or in-app notification for the resulting personalized learning assignments. They are aware of the assignment and therefore don't need to be additionally notified. 
This behaviour is intentional and part of the platform design.
 
However, if the same assessment is assigned to another user with Automatically assign personalized training enabled, that user will receive the normal assignment notifications (email and in-app alerts).
This difference can occasionally create confusion when administrators test assessments using their own account, as the expected learner notifications will not appear.
 

 

Assessment Assignment Notifications (User-Facing)

When a user is assigned a KnowledgeSmart Skill Assessment, they receive a dedicated assessment invitation. It behaves differently from standard notifications:

  • Sent using either:
    • Default KS template
    • Custom template from assessor/administrator
  • Optional KnowledgeSmart reminders may follow
  • KS emails operate outside Pinnacle’s email toggle
  • The assignment still appears in the Peak notification bell

 

Reminder Timing (User-Facing)

  • 14 days before due date
  • 7 days before due date
  • Within 24 hours after due date (past-due alert)

 

Assignor & Assignment Admin Notifications (Admin-Facing)

  • Learner drops an assignment
  • Learner marks an assignment complete
  • System verifies true completion
  • An assignment becomes past due

Admin Experience:

  • Notifications appear in Admin Portal activity feed
  • Used for progress and overdue monitoring
  • Never shown to end users

 

Manual Email Reminders (Admin-Initiated)

Admins and assignors may send a manual reminder using “Send Email” within the assignment options menu.

Notification Delivery Flow

A simplified view of how user and admin notifications behave.

User Flow

  • Appears in Peak bell immediately
  • If opened → email suppressed
  • If unread → checked in 5-minute batch
  • If unread + email enabled → email sent

Admin Flow

  • Appears in Admin Portal only
  • Used for oversight
  • Never emailed
  • Email reminders must be manually initiated

 

Assignment Email Logic - Feature Emails vs. “Missed Bell Notification” Emails

It’s important to separate feature-driven assignment emails from the platform’s automatic “missed notification” emails.

A) “Missed Bell Notification” Emails (Global Toggle)

  • Controlled by Settings → General → “Allow Users to Receive Notifications via Email”
  • Only applies to unread in-app bell notifications that remain unseen after the ~5-minute window
  • If the user opens the bell notification before the batch runs → no email is sent

B) Assignment Feature Emails (Assignment Controls)

  • Sent only when an admin/assignor explicitly enables an assignment email option (e.g., “Send Email” / reminder actions)
  • Not governed by the global “missed notification” email toggle
  • Assignment activity still creates a bell notification, which may separately trigger a “missed notification” email if unread and email is enabled

Practical takeaway: An assignment may generate both a bell notification and a feature email — but they are controlled by different settings.

 

Key Takeaways

  • The global email toggle controls only automatic emails for unread bell notifications.
  • Assignment emails are feature-driven and depend on the assignment’s own email/reminder actions.
  • Assignments still create bell notifications, which may separately trigger a “missed notification” email if unread and email is enabled.

 

3) Content Manager Manual Notifications

 

Why It Matters

Manual notifications allow Content Managers to highlight important updates, promote new content, and draw user attention to resources that matter. Thoughtfully crafted notifications drive adoption without causing alert fatigue.

 

How to Send a Notification

  • Navigate to the Content area of the Admin Portal
  • Select Send Notification from the Action Menu (⋯)

 

Best Practices for Content Notifications

  • Set Clear Titles: Use concise, action‑driven titles that immediately signal value (e.g., “New Revit Workflow Added”).
  • Write Meaningful Messages: Keep the message short and focused on why the content matters.
  • Use Associated Content: Always link directly to the resource using the Add Content button to increase engagement.
  • Target the Right Audience: Notifications should be scoped to the groups or roles that will benefit from the update.
  • Avoid Overuse: Reserve notifications for meaningful updates—avoid sending multiple alerts in a short time frame.
  • Use Visual Cues: If applicable, upload a thumbnail or select content with strong visuals to increase click‑through.

Recommended Use Cases

  • Announcing a new set of workflows or process guides
  • Highlighting time‑sensitive or mandatory training
  • Promoting new content Collections or Libraries
  • Sharing project‑specific learning resources
  • Driving awareness to under‑utilized high‑value content

 

Field Restrictions

Title Field:

  • Up to 100 characters
  • Alphanumeric & special characters allowed
  • No leading/trailing spaces
  • Required field

Message Field:

  • No character limit
  • Optional field
  • Alphanumeric & special characters allowed

Final Thought: Manual notifications are most effective when used sparingly and strategically. Prioritize clarity, relevance, and user value to maintain trust and engagement.

 

4) Library Notifications

 

What Triggers Library Notifications?

Library notifications are generated when content is shared into a Library that has notifications enabled. These alerts ensure users know when new resources have been published to Libraries they can access.

 

Automatic vs. Optional Notifications

The notification behavior depends on how many users have access to the Library:

Libraries with fewer than 200 users:

  • Notifications are sent automatically when content is added

Libraries with 200 or more users:

  • An additional confirmation popup appears
  • Admins may choose between:
    • Send Notification – notifies all eligible users
    • Add Without Notification – adds content silently with no notification

 

User Experience

  • Library notifications appear in the Peak notification bell
  • If the user reads the notification before the email batch runs (every 5 minutes) → no email is sent
  • If unread + email toggles enabled → the user receives an email
  • Clicking the notification opens the Library directly

 

Admin Experience

  • Admins share Libraries with users, groups, roles, or the organization
  • Notifications are system-generated and cannot be customized
  • Notification behavior depends on access volume (automatic vs. confirmation pop-up)
  • Email delivery follows the Admin + User toggle logic

See  Managing Library Notifications  for more detailed guidance.

 

5) SPARK Notifications

 

What Triggers SPARK?

SPARK is Pinnacle Series' intelligent recommendation system. SPARK notifications highlight relevant content based on user activity, role, Library access, and organizational goals.

  • User completes content → SPARK suggests next steps
  • User interacts with specific topics → SPARK surfaces related resources
  • New high-value content is added → SPARK promotes it
  • SPARK campaigns configured by admins trigger targeted nudges

 

User Experience (What Learners See)

  • SPARK notifications appear inside the Peak notification bell
  • SPARK suggestions also appear in the user's SPARK panel
  • Opening a SPARK notification suppresses email
  • If unread + email enabled → email is sent

 

Admin Experience (SPARK Configuration)

  • Admins enable or disable SPARK at the organization level
  • Admins configure SPARK rules and campaigns
  • Admins cannot manually send SPARK notifications—they are algorithm-triggered
  • Email logic still follows the global + user toggle model

See  Managing and Customizing Spark Notifications  for more detailed guidance.

 

Tip:

SPARK works best when Libraries and metadata are well-organized, ensuring recommendations are accurate and high-value.


 

Still Need Help?

Log a support ticket