Skip to main content

How to automate badge assignments

Use automated rules to add or remove badges on users based on a People Segment.

Written by Michael Wallace

Scenario

As an admin or site owner, you want to automate the assignment of badges to users — for example, granting a "Mentor" badge to anyone designated as a mentor in PlusPlus, or a "10x Learner" badge to anyone who has completed at least 10 content assignments.

Solution

  1. Make sure a People Segment exists for the people the rule should affect.
    For more on segments, see How to use dashboard segments.

  2. Make sure the target badge exists.
    For more on creating and managing badges, see PlusPlus 101: Celebrate team members with user badging.

  3. Create a new automated rule with Add/remove badges from users as the action.
    For the full procedure, see How to create an automated rule.

  4. Configure the action's fields:

    • Add or remove — whether the rule grants or revokes the badge.

    • Badge — the badge to add or remove.

  5. Click Publish.

The rule runs on its scheduled cadence, granting or revoking the badge for everyone in the segment.

Go deeper

Add and remove are separate rules

A single rule can either add or remove a badge, but not both. To bidirectionally manage a badge — granting it when someone enters a state and revoking it when they leave — create two rules:

  1. An Add rule whose segment matches everyone who should currently have the badge.

  2. A Remove rule whose segment matches everyone who should not have the badge — typically the inverse of the Add rule's segment.

The two rules typically operate on disjoint sets of people, so order on the Automated Rules dashboard does not usually affect the outcome. If your Add and Remove segments overlap, expect ordering to matter — see Reference: How automated rules run for ordering mechanics.

Skip behavior

The rule checks each person's current state before acting:

  • An Add rule skips people who already have the badge.

  • A Remove rule skips people who do not have the badge.

This means the rule is safe to leave running indefinitely; people in the desired state are not re-processed on every run.

Combining with manual badge assignment

The rule operates on the badge globally — there is no distinction between badges added manually and badges added by rules. An Add rule skips people who already have the badge, regardless of how they got it; a Remove rule revokes the badge from anyone in the segment, regardless of how they originally got it.

If you need to preserve manually-granted badges, do not use an automated Remove rule on the same badge. Alternatively, limit the Remove rule's segment so that manually-recognized people don't match.

Did this answer your question?