Badging Configuration

Badging Configuration#

Badge templates, requirements, rules, and penalties are configured in the Credentials admin panel. Each badge template needs at least one requirement and must be activated before it takes effect.

Badges administration

Provider Setup#

Provider setup (organization credentials, template synchronization) differs per badging provider.

Badge Requirements#

Requirements describe what must happen for a learner to earn a badge. At least one requirement must be associated with a badge template.

Badge requirements are listed inline on the badge template detail page.

Badge template requirements

A badge template can have multiple requirements. All requirements must be fulfilled before the system issues a badge.

Each requirement has the following fields.

  • Event type - the event that must occur. Available event types are pre-configured in the application settings.

  • Rules - a list of configured data rules (if any). See Data Rules.

  • Description - an optional human-readable reminder about the requirement’s purpose.

  • Group - by default each requirement belongs to its own group. You can assign two or more requirements to the same group - the group is fulfilled when any of its requirements is fulfilled (“OR” logic inside a group).

Badge requirement rules group

Note

Any public signal from the openedx-events library can be used, provided it includes user PII (UserData) so learners can be identified.

See Configuration Examples.

Data Rules#

Data rules narrow a badge requirement based on the expected event payload.

To add or edit a data rule:

  1. Navigate to the badge requirement detail page (use the Change inline link).

  2. Find the “Data Rules” section and add a new item.

Badge requirement rules edit

Each data rule describes a single expected payload value. Key paths are generated from the event type of the parent requirement.

Badge requirement data rules

Field

Description

Key path

Dot-separated path to the target attribute. Each event type has a pre-defined set of key paths.

Operator

Comparison operation: "=" (equals) or "!=" (not equals).

Expected value

The value to compare against.

Note

For boolean fields, the following string values are accepted:

  • True: "true", "True", "yes", "Yes", "+"

  • False: "false", "False", "no", "No", "-"

See Configuration Examples for details.

Badge Penalties#

Penalties reset badge progress based on learner activity. They are optional - a badge template can have zero or more.

Each penalty targets one or more badge requirements. A penalty uses the same structure as a requirement, but decreases progress instead of advancing it. When all penalty rules match, the learner’s progress toward the badge resets.

Badge penalty rules edit

Activation#

After configuring requirements, activate the badge template:

  1. Navigate to the badge template detail page.

  2. Check the Is active checkbox.

Important

An activated badge template starts working immediately.

Badge template detail page

Core credential attributes

Shared across all credential types.

Badge template credential attributes

Specific to badges.

Provider-specific attributes

State, dashboard link, etc. Varies by provider (see Credly Configuration or Accredible Configuration).

Configured requirements

See Badge Requirements.
Contents