> ## Documentation Index > Fetch the complete documentation index at: https://docs.levelset.io/llms.txt > Use this file to discover all available pages before exploring further. # Discipline rules > Set the infractions and their points, how long points count, the disciplinary actions and their thresholds, which roles can file discipline, and the discipline form password Discipline in Levelset runs on points, and this page sets the rules. An **infraction** is something documented about a team member, and each kind is worth a number of points. Points count for a window of days, and when a person's total reaches a **threshold**, Levelset recommends the **disciplinary action** tied to it, such as a documented warning. [Discipline](/discipline/overview) is where those infractions and recommendations show up day to day; this page is where your organization decides what they are. Open **Performance > Set up > Discipline rules**. It has three tabs: **Infractions**, **Actions** and **Access**. Infractions, actions and the role checkboxes apply to every store; the points window can differ per store and the leader code is per store. Anyone who can sign in can open the page and read it; changing each tab takes a permission, listed in [Who can do what](#who-can-do-what). Say your store's policy counts a tardy for a few points, keeps points for 90 days, and calls for a documented warning at the first threshold your organization chose (use your own infractions, points and actions). The sections below set it up. ## Define infractions and their points On the **Infractions** tab, each row is one thing that can be documented, with its **Infraction Name** and **Point Value**, and two boxes: **Req. TM Sig.** makes the team member sign on the device before the form can be submitted, and **Req. Leader Sig.** does the same for the person filing. Click **Add Infraction** for a new row, the trash icon to remove one, and **Save Changes**. A point value can be negative. A row such as "Covering a shift" with negative points subtracts from the total, so the team's discipline history shows the good as well as the bad. ## Set how long points count On the **Actions** tab, **Points Window** decides how long an infraction keeps counting. **Days counted** takes 14-365; at 90, an infraction from 91 days ago no longer counts against the person. **Action due within** is how many hours (1-720) after Levelset recommends an action it is expected to be recorded. **Hard reset on a schedule** clears everyone's points on a repeating date instead of relying only on the rolling window: every 1-24 weeks or months, on a weekday or a day of the month, counted from the **Starting from** date. Click **Save window**. The **Store** dropdown at the top keeps one window for **All stores (default)** or sets a different one for a single store. A store with its own window is marked "customized", and **Use the default for all stores** puts it back. ## Define the actions and their thresholds Lower on the **Actions** tab, **Disciplinary Actions** lists each step with an **Action Name** and a **Point Threshold**. When a team member's points in the window reach a threshold, Levelset recommends that action on **Performance > Discipline**, where it is recorded once it has been carried out. Rows sort themselves from lowest threshold to highest, so add them in any order with **Add Action**, then **Save Changes**. Set each step and its threshold from your own policy: in the example, a documented warning at the first threshold, and stronger steps at higher ones. Levelset only recommends; a person still decides what happens and records it. ## Choose which roles can file discipline On the **Access** tab, **Role Permissions** lists your roles in order with a checkbox each. A checked role can be named as the leader on the discipline form in the mobile web app. The two roles at the top of your organization's order are always checked and can't be unticked; the third is checked unless you untick it; every role below that stays unchecked until you tick it; and the bottom role is never offered on the form. A change saves at once and applies at every store. Your roles themselves are set on [Team & Access > Roles](/team/roles). ## Set the leader code **Form Password**, further down the **Access** tab, holds the **leader code**: the per-store code someone types before the discipline form opens in the **mobile web app**, the no-sign-in web page that opens a store's forms on a phone. It is the store's discipline form password, the same one shown under **Organization > Set up > Team links**, and changing it in either place changes it for that store. What it protects, and what happens when it is left empty, is explained in [Team links](/organization/team-links). ## Get told when something is filed Alerts for infractions and actions are automations, not a setting on this page. Set one up under **Workflows > Automations**; see [Automations](/forms/automations). ## Who can do what If a tab described on this page is read only for you, this table names the permission behind it. | If you notice this | The permission behind it | | - | - | | The **Infractions** tab is read only | Discipline > Manage Infractions Settings | | The **Actions** tab is read only | Discipline > Manage Actions Settings | | The **Access** tab is read only | Discipline > Manage Access Settings | If you're missing something here, ask whoever manages roles in your organization to turn it on. See [Roles](/team/roles). ## Common questions No. You can set how long points count and a scheduled reset, but a limit on repeating one action is not built. The form password, and the points window when a store is picked in its **Store** dropdown. Infractions, actions and the role checkboxes apply to the whole organization. No. Each infraction keeps the points it was filed with, and the new value applies to infractions filed from then on. To correct an older one, open it from the person's **Discipline** tab; see [Correct or remove an infraction or action](/discipline/overview#correct-or-remove-an-infraction-or-action).