Assignment Maps vs Classic Blueprints

By Emalee Firestein

Assignment Maps are a new type of Blueprint offering additional scoping flexibility over Classic Blueprints on a highly visual interactive map

Kandji recommends Assignment Maps for any size deployment as they provide the flexibility needed to grow, and most importantly, adapt, over time as things change without the need to create many like-Blueprints with only a few small differences. For very straightforward deployment use cases, like kiosk iPads, Assignment Maps can easily accommodate them with the simplicity of Classic Blueprints simply by using the All Devices node.

Below is a comparison chart of Classic Blueprints and Assignment Maps

FeatureClassic Blueprints 
Assignment Maps

On-device remediated compliance controls for macOS with Parameters

Ability to create using pre-built security compliance templates

Easy assignment of Library Items to all devices on the Blueprint

Audit Activity

Compatible with Automated Device Enrollment

Compatible with manual Device Enrollment


Assignment Rules

Defined per Library Item 

Enterprise API support

For everything except the shape and form of the map

Nested Assignment Rules

Reusable Assignment Rules

Logical grouping of Library Items

Multiple Self-Conflicting Library Items in the same Blueprint

Dedicated troubleshooting view to show how Assignment Rules have affected Library Item assignment

Both types of Blueprints appear in Kandji wherever a Blueprint can be selected, such as when editing a device, or on the Add Devices page for device enrollment.

Further Reading

To learn more about Assignment Maps, check out our other articles: