Understand Notifications

---

At a glance

OneClick Notifications are Inapp and Push alerts that let your team stay informed about activity across four modules: Checklists, Moola, Rotating Buddies, and Infractions. Notifications are configured at the store level by a Director or higher, with separate toggles for Inapp and Push on each specific notification type. Two global silence switches (Silence App Notifications and Silence Chat Notifications) give a store quick all-off control without losing the per-type configuration underneath. Weekly recap summaries supplement the event-level alerts so leaders and team members have both real-time awareness and a weekly digest of where things stand.

Before you start

This is a reference article. Read it once, return when needed.

Core reference content

What Notifications are

A notification is a real-time alert that fires when something noteworthy happens in OneClick. There are two delivery channels:

1. Inapp notifications render inside OneClick (for example, a badge on a module or a toast in the UI). They do not require the user's device to be unlocked or online outside the app.
2. Push notifications go to the device's operating-system notification center (for example, the iOS or Android notification tray). They reach the user even when OneClick is not open.

Each notification type can be configured for Inapp only, Push only, both, or neither. The third option lets a store enable a notification for in-app visibility without waking up every team member's phone.

The four notification categories

Checklists. Team members are notified when a checklist is assigned to them. Shift leaders are alerted when a checklist is ready for review, or completed. A weekly recap summarizes overall checklist progress for the week.

Moola (Rewards). Weekly balance summaries go to all users. Leaders see updates with top balances across their teams. Individual users get transactional alerts when Moola is earned, spent, charged, requested for redemption, approved, or rejected.

Rotating Buddies. Users are alerted when a rotation is due and when a rotation is confirmed or completed. This supports the Rotating Buddies counting workflow by automating the prompts that used to require manual tracking.

Infractions. Users are alerted when an infraction is issued to them (if the team-member-receipt email is enabled under Infractions settings), and leaders are alerted when a team member reaches a low, mid, or high point threshold. This ties the Infractions threshold-notification feature (configured in Settings > Infractions) into the broader notification system.

Store-wide configuration

Director permission or higher is required to enable or disable notification types store-wide. These settings affect everyone in the store, not a single user. The logic is deliberate: notification behavior is a store policy decision, not an individual preference, because inconsistent notification configuration across users causes coordination gaps (the team member thinks they were notified; the leader does not know why they weren't).

The settings surface

Notification settings live under Settings > Notifications. The page has two zones plus a test utility:

1. Global silence toggles (top zone). Two toggles: Silence App Notifications and Silence Chat Notifications. Flipping either one disables that whole channel without erasing the per-type configuration underneath. Useful during store downtime, training periods, or when the team needs a quiet day without losing the carefully tuned per-type setup.
2. Per-category notification alert sections (bottom zone). Four dropdown sections, one per category (Checklist Notifications Alerts, Moola Notifications Alerts, Rotating Buddy Notifications Alerts, Infraction Notifications Alerts). Each section expands to a table listing specific notification types with three controls per row: Inapp (checkbox), Push (checkbox), and Enabled (toggle). A red circle on a checkbox indicates the recommended setting for that channel; these are guidance only, not a lock.
3. Test Push Notification button (top-right). Sends a test Push notification to confirm delivery is working without waiting for a real event. The test notification arrives with the title "Complete Your Profile Setup". this is a known cosmetic issue, not a misconfiguration.

Notification types per category

Checklists:

1. List Ready For Review. Notifies shift leaders when a team member has completed a checklist that needs approval.
2. Assigned To Checklist. Alerts a team member when a leader has assigned a checklist to them.
3. List Completed. Confirmation that a checklist was successfully completed.

Moola:

1. Get Moola. Alerts when the user receives Moola, with the reason.
2. Charged Moola. Alerts when someone charges the user Moola, with the reason.
3. Moola Redemption Requested. Informs anyone with Moola settings access that a team member has requested a reward. Additional leaders or team members added to the specific item in Moola settings also get notified.
4. Moola Redemption Approved. Informs the requesting team member that their redemption was approved.
5. Moola Redemption Rejected. Notifies the requesting team member that their redemption request was not approved.

Rotating Buddies:

1. Rotating Buddies Rotated. Confirms that a team member and their assigned buddy have successfully rotated roles.

Infractions:

1. Accountable. Fires when an infraction is issued.
2. Point Threshold Low. Notifies when a team member reaches the low accountability threshold that requires action.
3. Point Threshold Mid. Alerts when a team member reaches the medium threshold that requires follow-up.
4. Point Threshold High. Warns when a team member reaches the maximum threshold before termination.

The three Infractions threshold notifications correspond to the low, mid, and high point values configured in Settings > Infractions > Threshold Notifications. Configuring both surfaces (the Infractions threshold point values and the Notifications enable/disable controls) makes threshold alerting reliable.

How Notifications relate to other modules

Infractions. The Notifications page enables the threshold-alert channel; the Infractions settings page configures the point values and recipient list. Both need to be set for threshold alerts to fire.

Moola. The Notifications page controls whether the Moola transactional alerts fire; the Moola settings page controls who is notified for redemption requests beyond the default redemption-settings-access group.

Checklists. Checklist notifications are driven by the Checklists module's completion and review workflow. The Notifications page just gates whether the alerts deliver.

Chat. Chat has its own Silence Chat Notifications toggle at the top of the Notifications page. The Chat module also supports per-channel muting (Mute Channel from the channel's three-dot menu) that applies to a single channel rather than all chats.

Video

Not planned for this reference article.

Common gotchas

I enabled a notification type but the team is not getting notified.

Three places to check. First, confirm the Enabled toggle is on, not just the Inapp and Push checkboxes. Second, confirm at least one delivery channel (Inapp or Push) is checked; a type with Enabled on but both channels unchecked is effectively off. Third, confirm the global Silence App Notifications toggle at the top is not flipped on; the global switch overrides all per-type configuration.

I silenced notifications for a quiet period but now no one is getting anything even though I turned it back on.

Allow a few minutes for the toggle state to propagate to devices. If users still report missing notifications, ask them to log out and log back in; app state sometimes caches the silenced state until a session refresh.

The Push notifications are working for some team members but not others.

Push notifications depend on device-level permission granted by each team member when they first installed the app. A team member who denied notifications at install time, or who disabled them later in their device settings, will not receive Push alerts even if the store configuration is correct. Check device settings on affected team members' phones.

Threshold notifications from Infractions are configured but no one is being notified.

The Accountable, Point Threshold Low / Mid / High notifications under the Infractions category need to be Enabled here AND the recipient list and point values need to be configured under Settings > Infractions > Threshold Notifications. Both surfaces must be set up.

A Manager wants to adjust notifications for their team but cannot find the settings.

Notification settings are Director-restricted by default because they affect the entire store. A Manager would need Director-level permission to change these settings. If your store structure requires Managers to tune notifications, raise the permission separately; otherwise, the Director or Operator should handle the configuration.

A team member does not want to receive Moola balance summaries.

Notifications are store-wide, not per-user. There is no individual opt-out for a notification type today. If a team member wants fewer notifications, they can mute at the device level (turn off Push for OneClick) or log out when off-shift to stop Inapp alerts.

Related articles

1. Configure Notification Settings (How-To Guides)
2. Turn Off Email Notifications for a Checklist (How-To Guides)
3. Understand Infraction Types and Severity (Reference), for threshold-notification point configuration
4. Understand Moola (Reference), for Moola redemption notification recipients
5. Understand Chat Channels and Direct Messages (Reference), for Chat's channel-level muting
6. Understand Permission Levels (Reference)

Still stuck

If notification behavior does not match this reference, submit a support ticket and include your store number, the specific notification type and category, the current setting (Inapp / Push / Enabled state), and a description of what you expected versus what happened. Support typically responds within one business day.

---

Pre-publish checklist

28 334109b4-bb84-46b2-b70d-614b07dadd9f complete Seven sections filled (Reference adaptation).

29 5a8c0e01-0754-4a24-a22b-c6868d9445f3 complete At a glance within template spec.

30 a6d34eb4-c6e6-4473-9faa-a01b99a28fa9 complete No em dashes, no hedge words.

31 d11ef370-1c27-469c-a995-8ebd6a779486 complete Permission-based role references; Director-default for store-wide control documented.

32 eacc213f-efec-4c05-ae9d-73e17118d644 complete Four notification categories enumerated with all individual notification types.

33 9487d198-2521-4c35-947b-81ffb10f43cb complete Cross-module dependencies documented (Infractions thresholds, Moola redemption recipients, Chat muting).

34 13e09c96-1d6d-48f9-bcd1-12d81404ba47 complete "In-App" column label corrected to "Inapp". verified live 2026-05-04.

35 2371053e-e767-4970-92ce-b007e808a6e5 complete 5th Moola type added (Moola Redemption Rejected). verified live 2026-05-04.

36 a088a982-0935-4d4f-bd8e-1c0331833043 complete Test Push Notification button documented. verified live 2026-05-04.

37 a39a5db6-9d89-414f-b306-c4959c1dd5c6 incomplete UI verified against Production (screenshot pass still needed).

38 9e9eb8e4-ced4-4d6f-8ce2-4cf4a30e2285 incomplete Screenshots to be inserted (Settings > Notifications landing page with silence toggles, expanded category dropdown showing the Inapp / Push / Enabled table).

39 af1c9b58-ed01-4637-9b81-fcc573519cca incomplete Reviewed by Jared and Kevin.

Why this article exists

"Why didn't I get notified?" is one of the most common operator-to-support questions, and the answer depends on four independent configurations (the Enabled toggle, the Inapp and Push channel checkboxes, the global silence toggle, and, for Infractions threshold notifications, the upstream point-value configuration). A Reference article that lays out all four surfaces in one place, plus the four notification categories and their specific types, lets leaders diagnose their own configuration before opening a ticket. Direct ticket-deflection value against a high-volume category.