A sticker on a student's digital ID is more than just a visual of what privileges they have or which clubs they are members of. They can also signify outstanding detentions, suspended privileges, tardy thresholds reached, and add that student to a named sticker list. That list controls what the student can and cannot check in to.

This guide covers how to assign a sticker through a consequence, restrict access using the sticker list, and configure automated removal when the student completes the required action. No manual removal required.

Permission level required: Owner | Manager | ID Manager | Behavior Manager

⚠️ Before you begin: This guide assumes your consequence types and automation framework are already configured in Minga. If you have not set those up yet, complete your consequence and automation setup before proceeding.

In this guide:

Step 1: Decide what your sticker represents: Define the status your sticker signals and which students it applies to.
Step 2: Create the sticker: Build the sticker in ID Manager and configure what it looks like on the digital ID.
Step 3: Attach the sticker to a consequence: Configure the consequence to apply the sticker automatically when issued.
Step 4: Configure automated sticker removal: Set up the behavior and automation chain that removes the sticker when the student completes the required action.
Troubleshooting
FAQs
Resources

Step 1: Decide what your sticker represents

Before you configure anything in Minga, decide what status or meaning your sticker will signal and what consequence it should accompany. Stickers work best when they represent a clear, specific condition with a defined resolution path.

Ask yourself these questions before building:

Decision	What to determine
What status does this sticker represent?	Examples: detention, tardy threshold reached, privilege suspended. The sticker name and image should match this status clearly.
What triggers the sticker to be applied?	A specific consequence step in your automation — for example, the consequence issued at the 5th tardy. Identify which consequence this is before proceeding.
What removes the sticker?	The action the student must complete. Examples: checking in to serve a detention, a counsellor logging a meeting, a staff member manually clearing the record.
Which check-in reasons should be restricted?	List every check-in reason a student on this sticker list should be blocked from — for example, off-campus lunch, library, or sporting events.
Who manages exceptions?	Decide now which role (Owner, Manager) can manually override a sticker if needed.

💎 Tip: Document your answers before configuring. The behavior, consequence, check-in reason, and sticker all need to reference each other. A clear plan prevents misconfiguration.

✅ Outcome: You have a clear policy decision: what triggers the sticker, what it restricts, and how it is removed.

Step 2: Create the sticker

Create the sticker in ID Manager. The sticker name and image are what staff and students will see on the digital ID, so make them immediately recognizable.

Step-by-step guide to creating a sticker

Navigate to ID Manager > Stickers.
Click Create sticker.
Enter a name in the Sticker name field.
- Use a name that immediately communicates the student's current status to any staff member who scans their ID. For example: Detention Outstanding, Off-Campus Suspended, or Tardy Threshold Reached.
Upload or select a sticker image.
- The image appears on the student's digital ID when the sticker is active. Choose something visually distinct so staff can identify it at a glance.
Click Save.

✅ Outcome: The sticker exists in Minga and is ready to be attached to a consequence.

Step 3: Attach the sticker to a consequence

Attaching a sticker to a consequence means every time that consequence is issued, either manually or through an automation, Minga applies the sticker to the student's digital ID automatically. No staff action required.

Step-by-step guide to attaching a sticker to a consequence

Navigate to Behaviors > Consequences.
Select the consequence you identified in Step 1 — the one issued when the sticker should be applied.
Click on the blue edit pencil to open the consequence settings.
Locate the Sticker heading.
Enable Assign or remove sticker.
Select the sticker you would like to assign from the dropdown menu.
- This field connects a sticker to the consequence. When the consequence fires, the sticker is applied.
Select the sticker you created in Step 2.
Click Save.

✅ Outcome: Every time this consequence is issued, Minga automatically applies the sticker to the student's digital ID and adds them to the sticker list.

Step 4: Configure automated sticker removal

Stickers do not remove themselves when a consequence is manually marked complete. Removal requires a consequence that removes the sticker to be assigned to the student. A typical use case for this would be for detentions and detentions served:

Student is assigned a detention consequence that adds a sticker to their ID.
Student is checked in to serve their detention. The check in reason is configured to automatically complete the most outstanding consequence.
This same check in reason will also assign a behavior upon check in.
This behavior is tied to an automation group that assigns a consequence (a different consequence from the one just served and marked complete). This consequence is set up to remove the sticker from the student's ID.

🔘 How the removal chain works: Check-in reason → issues a behavior → behavior triggers automation → automation issues a consequence → consequence removes the sticker.

Part A: Create the "completion" behavior and consequence

Create a behavior specifically for this sticker removal chain. Do not reuse an existing behavior — keeping it separate prevents the removal from triggering in unintended situations.

Step-by-step guide to creating a 'completion' behavior

Navigate to Behaviors from the main menu.
Select the Behaviors tab.
Click the blue Create behavior button.
Enter a name for your behavior. Pro tip: make it an identifiable name that lets you know it is the trigger to the consequence that will remove the sticker.
Click Save.

Step-by-step guide to creating a 'completion' consequence

From the Behaviors area in Minga, select the Consequences tab.
Click Create consequence.
Give your consequence a name. Pro tip: you can name it similar to the behavior that will trigger it.
Select Other from the Type of consequence dropdown.
Under the Sticker heading, enable Assign or remove sticker.
Select the sticker to be removed in the Removed sticker dropdown.
Click 'Create' to save your new consequence.

Part B: Configure the check-in reason to issue the behavior

The check-in reason is the action the student takes to clear their sticker. When they check in using this reason, Minga logs the completion behavior.

Step-by-step guide to configuring a Check In reason

Navigate to Check In > Check-In Reasons.
Select the check in reason that auto completes the outstanding consequence that assigned the sticker. For example, a detention check in.
Under the Automations heading, select your newly created behavior from the Auto assign behavior drop down.
Click Save.

Part C: Create the automation that fires on the completion behavior

The automation watches for the completion behavior and issues the removal consequence when it fires.

Step-by-step guide to creating the Automation Group

Navigate to Behaviors and select the Automations tab.
Click Create new automation group.
Enter the name of the Automation group and an optional internal description.
Under Behavior triggering automation, select the behavior created in Part A.
Select Create.
In the panel Add automation for 'name of automation group,' enter a name for the step in your automation group.
Enter the number of behaviors that will trigger the consequence. For this group, enter 1.
Select the consequence created in Part A.
Select Add.

⚠️ Note: The sticker is not removed until every link in this chain completes. If the check in reason, behavior, automation, or removal consequence is misconfigured at any point, the sticker will remain on the student's ID.

✅ Outcome: The automated removal chain is in place. When a student checks in using the configured check-in reason, Minga logs the behavior, fires the automation, issues the removal consequence, and clears the sticker from the student's digital ID.

Troubleshooting

A student’s sticker did not apply when the consequence was issued.

If the sticker does not appear on a student’s digital ID after a consequence is issued, the sticker is likely not attached to the consequence. Navigate to Behaviors > Consequences, open the consequence, and confirm the correct sticker is selected in the Sticker field. If the field is empty, select the sticker and save. The sticker will not apply retroactively to consequences already issued — you will need to apply it manually to the affected student’s profile.

The sticker is not removing after the student checks in

If the sticker remains on a student’s ID after they check in using the completion check in reason, one or more links in the removal chain are broken. Work through the chain in order: confirm the check in reason is configured to issue the completion behavior, confirm the automation trigger matches the behavior name exactly, and confirm the automation’s consequence action is set to Remove sticker with the correct sticker selected. If all three are correct and the sticker still does not clear, contact Minga support.

A staff member applied or removed a sticker manually but it triggered an automation

Manual sticker changes do not log a behavior and do not trigger automations. If an automation fired after a manual sticker change, another event, like a behavior assignment, a check in, or a scheduled automation, is the likely cause. Review the student’s behavior log to identify what triggered the automation.

FAQs

Can a sticker be applied by more than one consequence?

Yes, the same sticker can be attached to multiple consequences. Any student who receives any of those consequences will be added to the sticker list and subject to the same check-in restrictions. For example, a Detention Outstanding sticker could be applied by both a tardy consequence and a behavior referral consequence. Both will add the student to the same list.

Can a staff member remove a sticker manually without going through the automation chain?

Owner, Manager, and ID Manager roles can remove a sticker manually from a student's profile.Manual removal takes effect immediately and removes the student from the sticker list. Manual removal does not log a behavior or trigger any automation.

What happens if a student reaches the tardy threshold again after their sticker was removed?

If the consequence configured to apply the sticker fires again, for example, because the student reaches the tardy threshold a second time, the sticker is reapplied and the student is added back to the sticker list. The removal chain must be completed again to clear it.

How quickly does the sticker clear after a student checks in?

The sticker is removed after the full automation chain completes: the check in logs the behavior, the behavior fires the automation, and the automation issues the removal consequence. Under normal conditions this completes within seconds of the check in. If the sticker does not clear within a minute, review the chain configuration for a broken link.

Resources

Set up and Manage Open Detention: Configure the open detention check-in station and connect it to the sticker removal chain built in this guide.
Build a progressive discipline framework with automated consequences: Set up the tardy or behavior automation that issues the sticker consequence.
Configure Check In Reasons: Full reference for check-in reason settings, including access controls and behavior assignment.
Create and Manage Stickers: Full reference for the sticker manager, including manually applying and removing stickers from student profiles.

Use Stickers with Consequences and Automations