Blueprint Modifiers

Blueprint Modifiers

Modifiers are configured instances of Blueprints. They are associated with Asset Groups and run against Assets — specifically, against computers that have the K12Panel Agent installed. Modifiers do not run against Chromebooks or non-technical assets.

If a Blueprint is the recipe, the Modifier carries out that recipe against an Asset. You use Modifiers to make changes to computers, including:

• Install software
• Uninstall software
• Change security or other settings
• Force updates
• Anything else a Blueprint can do

Modifier Scope: Asset or Person

Modifiers always run on a PC, but their scope determines when:

• Asset-scoped — runs on the computer at startup, regardless of who uses it.
• Person-scoped — runs on the computer for a logged-in user who matches the Person-scoped criteria.

Viewing and Creating Modifiers

You need at least one Modifier of a Blueprint to associate it with an Asset Group (you can have more). View and create Modifiers from the Blueprint detail page.

A new Modifier inherits the Blueprint’s scope and category. Name it however you like — often similar to the Blueprint so its purpose is clear, or distinct enough to tell it apart from other Modifiers of the same Blueprint.

Priority

The Priority is the execution priority on an Asset. Higher priority runs earlier in the sequence. A new Modifier starts at the Blueprint’s suggested priority, which you can change to control ordering relative to other Modifiers.

Common Questions

Do Modifiers run on Chromebooks?
No. Modifiers run only on PCs with the K12Panel Agent installed.

What’s the difference between Asset-scoped and Person-scoped?
Asset-scoped runs at startup for the machine; Person-scoped runs for a matching logged-in user.

How do I control the order Modifiers run in?
Set the Priority — higher priority runs earlier.

Can a Blueprint have more than one Modifier?
Yes, and you need at least one to associate it with an Asset Group.