Configure Infraction Settings

v2 fixes (2026-05-04, validated vs live UI): Threshold notification = single "Enable threshold notifications" checkbox (not 3 configurable Low/Mid/High levels); Significant Point Threshold default = 5 (not 20); New Point Duration = dropdown selector (not free-text days); added "Include the issuing leader on CC line" checkbox; added "BCC Other Email Addresses" fields (up to 3); added "Reset Accountability to Defaults" red button section.

---

At a glance

Configuring Infraction Settings tunes how your store tracks disciplinary records: which infraction types are available, how points map to penalty labels, when threshold emails fire, who signs what, and how long points count toward the running total. Manager permission or higher is required because changes apply store-wide. Plan to spend ten to fifteen minutes for a first-time configuration; most stores revisit only when policy changes.

Before you start

1. You need Manager permission or higher to open the settings page. Configuration changes apply to every team member in the store, so the access floor is deliberately higher than the floor for issuing individual infractions.
2. Know your store's disciplinary policy before you start. The defaults are a starting template (point values, penalty labels, threshold counts); your store's HR policy should drive the final values.
3. Read Understand Infraction Types and Severity first if you have not already. The Reference article explains the model (points, penalties, expiration, the New Point Duration rolling window) so this How-To can focus on the configuration workflow.
4. Estimated time: ten to fifteen minutes for a complete pass.

Steps

Open the settings page

1. Open Settings from the left navigation menu.
2. Click Infractions. The settings page opens with sections for infraction types, penalty ladder, signatures, notifications, and New Point Duration.

Configure infraction types

Each infraction type has a name, a point value, and a default expiration. Types are what leaders choose from when issuing an infraction.

1. Review the default list (common examples: Tardy, Dress Code Violation, No Call No Show). Each type displays its current point value and expiration period.
2. To add a new type, press the + button at the bottom of the type list. Enter the name, point value, and default expiration period.
3. To edit an existing type, click the three-dot menu on the row. Select Edit, change any field, and save.
4. To remove a type, click the three-dot menu and select Delete. Existing infractions of that type remain on team member profiles as historical records; the type just stops being available for new issuances.

Name the types in leader-facing language. "No Call No Show" reads better than "NCNS" for a leader opening the Issue Infraction form in a hurry.

Configure the penalty ladder

The penalty ladder maps point totals to penalty labels. When a team member's running total reaches a threshold, the Accountability table on their profile highlights the corresponding penalty.

1. Scroll to the Penalties section of the settings page.
2. The default ladder is: 1 point -> Ineligible for promotion, 5 -> Written Warning, 8 -> Meeting with a director, 10 -> 3-Day Suspension without pay, 15 -> 5-Day Suspension without pay, 20 -> Termination.
3. Adjust any threshold's point value, label, or both by editing the row.
4. Add a new rung with the + button; remove a rung with the three-dot menu's Delete action.

Remember: the ladder labels what the team member has reached. The actual disciplinary action still happens outside the app through your store's policy. OneClick surfaces the signal; leadership acts on it.

Set the significant point threshold

The significant point threshold determines when the penalty label turns red in the Accountability table as a visual warning.

1. Find the Significant Point Threshold field (typically near the ladder section).
2. Enter the point value at which the label should turn red. Default is 5. Adjust up or down to match the point total at which your store wants the visual warning to appear.

Configure signatures and acknowledgement text

Each infraction captures a leadership signature and optionally an employee signature. Defaults: leadership Required, employee Optional. Both can be set per-store.

1. Scroll to the Signatures section.
2. Set Leadership signature to Required, Not Required, or Optional.
3. Set Employee signature to Required, Not Required, or Optional.
4. Fill in the Acknowledgement text field if your store wants a fixed statement that the signer is affirming (for example, "I have discussed this infraction with my team member and provided an opportunity for them to share their perspective"). Leave blank if no acknowledgement text is needed.

Apply global signature overrides (optional)

Three checkboxes at the top of the signature section override all per-infraction signature settings. Use these only when your store's paper-trail compliance demands them.

1. Allow edits to all infractions. If checked, any infraction can be edited regardless of other settings.
2. All submitted signatures editable. If checked, signatures can be changed after the infraction is submitted.
3. No signatures editable after submission. If checked, signatures lock on submission. This is the setting most compliance-focused stores use.

The third box overrides all other infraction editability settings. If locked signatures are required for your paper trail, check this box and confirm it overrides any per-type configuration.

Configure email notifications

Two kinds of emails can be enabled: team member receipt emails and leadership threshold notifications.

1. Scroll to the Email Notifications section.
2. For the team member email: flip Infraction Received on to send the team member an email each time they receive an infraction. Off by default.
3. Set the Reply-To Email address. Replies to infraction emails route here. Leave blank to send from a no-reply address.
4. Check Include the issuing leader on CC line to automatically copy the leader who issued the infraction on every team member notification email.
5. Enter up to three additional email addresses in the BCC Other Email Addresses fields to blind-copy other recipients on each notification.
6. For threshold notifications: check the Enable threshold notifications checkbox. When enabled, designated recipients receive an email alert when a team member's point total crosses the configured threshold.
7. Set the Repeat Notification interval (in days) to control how soon a threshold email can re-fire for the same team member. This prevents notification fatigue when a team member crosses the same threshold in close succession.

Threshold emails depend on both the Infractions settings (threshold enablement and recipients, configured here) and the Notifications settings (channel enablement on the Accountable and Point Threshold notification types). Both surfaces must be configured for threshold emails to fire. See Understand Notifications.

Configure the New Point Duration rolling window

The New Point Duration determines which infractions count toward the displayed total on a team member's profile. Infractions older than the window drop off the count even if their per-infraction expiration has not passed.

1. Find the New Point Duration field (typically in the main settings section).
2. Select a duration from the dropdown (for example, Two weeks). Today's date minus this duration equals the oldest date still counted.
3. Save.

Most stores use either per-infraction expirations or the New Point Duration window, not both. If both are configured, whichever removes the points first wins.

Save and verify

1. Save changes. Most fields auto-save; the page will indicate if an explicit save is required.
2. Open a team member's profile, click the Infractions tab, and confirm the Accountability table reflects the new ladder and thresholds. Verify a test infraction (issue one and then delete it) shows the expected point value, penalty label, and notification behavior.

Reset Accountability to Defaults (caution)

A red Reset Accountability to Defaults button appears at the bottom of the Settings > Infractions page. Pressing it resets the penalty ladder and point thresholds to OneClick's factory defaults, discarding all custom configuration. This action cannot be undone through the app.

Use this only if the configuration has become corrupted or you need to start from scratch. Confirm with your Director before pressing; the reset is irreversible.

Video

Video coming soon.

Common gotchas

I added a new infraction type but leaders still cannot see it when issuing.

Check that the type is saved and not marked as deactivated. If the type is active but still missing, ask the leader issuing the infraction to log out and log back in to refresh their session.

The penalty ladder was edited but the Accountability table on profiles still shows the old ladder.

Accountability table changes propagate on the next page load. Refresh the browser to see the updated ladder. If the old ladder persists on mobile, ask the user to close and reopen the app.

I configured threshold notifications but no one receives them when a team member hits the threshold.

Two places must be set. Here on the Infractions settings page, enable the Enable threshold notifications checkbox and confirm recipient configuration. On the Notifications settings page (Settings > Notifications), enable the Accountable and Point Threshold notifications with at least one delivery channel (In-App or Push) checked and the Enabled toggle flipped on. See Understand Notifications and Configure Notification Settings.

A team member is getting Infraction Received emails but leaders wanted that off.

Open the Email Notifications section and flip Infraction Received off. Existing emails do not unsend, but no new ones will fire.

Point values changed but old infractions still carry the old point values.

Infractions record the point value at issue time. Changing the type's default point value does not retroactively change existing infractions. If a historical infraction needs a different point value, a Manager can edit the individual record; for bulk historical adjustments, contact support.

Significant Point Threshold is set to a value but the label turns red at a different point.

Confirm the threshold is saved. Also check whether the penalty ladder has an entry at a lower point value with a label that implies terminal severity (for example, a rung labeled "Termination"). The red color triggers on both the significant point threshold AND the highest-severity ladder rung; both can produce red text independently.

I want to track positive behavior by awarding negative-point infractions.

Do not do this. OneClick is designed with Moola as the positive recognition system and Infractions as the negative-behavior tracker. Negative point values are not supported; mixing the two data sets is a long-term data-quality problem. See Understand Moola.

Two Managers saved changes to the settings page at the same time.

Last writer wins. Most fields auto-save on blur, so simultaneous edits can overwrite each other. Coordinate before making significant changes to this page, or have a single Director own the configuration for the store.

Our multi-store organization wants consistent settings across stores.

Settings are per store. No central template feature today. An Operator needs to apply the target configuration at each store individually. Document your target configuration (point values, ladder, thresholds, notifications) and walk through each store with a Manager to apply.

Related articles

1. Issue an Infraction (How-To Guides)
2. Understand Infraction Types and Severity (Reference)
3. Understand Notifications (Reference), for how threshold emails get enabled on the notification side
4. Configure Notification Settings (How-To Guides), for the paired notification-enablement workflow
5. Understand Permission Levels (Reference)
6. Request a Permission Change (How-To Guides), use this if you need Manager-level settings access

Still stuck

If settings are not saving, threshold notifications are not firing even after enabling on both the Infractions and Notifications pages, or the Accountability table is not reflecting the new ladder, submit a support ticket and include:

1. Your store number.
2. A screenshot of the Settings > Infractions page showing the current configuration.
3. A screenshot of the Settings > Notifications page showing the Infractions category.
4. The team member and infraction you were testing with, if applicable.
5. What you expected to happen versus what happened.

Support typically responds within one business day.

---

Pre-publish checklist

21 0fbf3b4b-ea3b-44a2-b689-0d4fec9d3345 complete Seven sections filled.

22 75190aa6-5145-471e-90bf-25db176bd3e1 complete Final step is a confirmation step (verify with a test infraction).

23 6cecbc79-31eb-4998-9646-60bf002600e8 complete No em dashes, no hedge words.

24 b68b157a-7a33-4f70-917b-104f3818b5fd complete Permission-based role references throughout; Manager+ settings access documented.

25 3fc00d3f-a1c6-4d75-b0bb-87f8c6741a11 complete Cross-reference to Understand Notifications + Configure Notification Settings for the paired threshold-email configuration.

26 6a2461a3-ff91-4f26-946d-501abd20d989 complete Anti-pattern callout (no negative-point infractions; use Moola for positive recognition).

27 934675d1-e159-4009-91fb-c2ae1fa5731d complete Concurrent-editing gotcha.

28 bc0179ea-305c-4454-b4f2-d53256330d17 complete v2 (2026-05-04): threshold = single Enable checkbox; default 5 (not 20); New Point Duration = dropdown; CC/BCC fields added; Reset Accountability to Defaults section added.

29 485c1779-9847-4a79-a7b5-685f9b4d3190 incomplete UI verified against Production.

30 50a45157-d87f-40fb-9080-990feaed0816 incomplete Screenshots at decision points (Settings > Infractions landing; Types list with + and three-dot menu; Penalties ladder; Signatures section with three global overrides; Email Notifications with Infraction Received toggle, CC/BCC fields, and threshold checkbox; New Point Duration dropdown; Reset Accountability to Defaults button).

31 eaaecdb8-e66b-40e5-880b-bc5691881fef incomplete Reviewed by Jared and Kevin.

Why this article exists

Surfaced by the Wave 1 cross-link map Pass 2 audit (Turn 38, Flag 38). Two Core articles (Issue an Infraction and Understand Infraction Types and Severity) both reference "Configure Infraction Settings" as a bonus, but no such article existed. The Infractions settings page is the deepest settings surface outside Permissions itself, covering types, ladders, signatures, notifications, and the rolling window; a How-To that walks through each configuration area should deflect tickets about why threshold emails are not firing, why a type is not appearing, and why signatures cannot be edited. High ticket-deflection value given Infractions module's complexity.

Source

Infractions PDF uploaded to KBRW Turn 26 (April 24, 2026). Same source as Issue an Infraction (Core slot 5) and Understand Infraction Types and Severity (Core slot 6). v2 corrections sourced from live UI validation pass (2026-05-04).