Blueprint inheritance not supported: manage cloned Blueprints as independent copies

Android

Title: Cloned and child Blueprints don't inherit changes — manage them independently

When you update a Blueprint that was cloned or assigned to a parent group, devices in subgroups or groups using the cloned Blueprint do not receive those changes.

Why this happens

When you clone a Blueprint, Esper creates a fully independent static copy with no link back to the original. Group hierarchy in Esper is an organizational structure only — it does not create a Blueprint inheritance chain. Each group applies exactly one Blueprint, and no settings cascade from a parent group's Blueprint down to subgroups.

Choose an approach for managing Blueprint updates

Because Blueprint inheritance is not supported, you must choose one of the two patterns below to keep settings consistent across groups.

Option A: Maintain a dedicated Blueprint per group (recommended)

This approach gives each group a single Blueprint containing all required settings — both shared base configuration and any group-specific overrides.

1. Open Blueprints in the Esper Console and identify every Blueprint that needs to receive the base-level change.
2. Open each Blueprint individually and apply the required change. Each Blueprint must be updated separately because there is no bulk-edit mechanism.
3. Use a consistent naming convention — for example, BaseConfig_v3 — SiteName — so you can track which version is active per group.
4. Navigate to Devices & Groups → [Group Name] → Blueprint and confirm the correct Blueprint version is assigned to each group.

Verify: On each group's Blueprint tab, the Blueprint name and version match what you just updated. Open an enrolled device in that group under Devices & Groups → [Device Name] → Activity Feed and confirm the updated settings have been applied. Device sync typically completes within 5 minutes of Blueprint assignment.

Option B: Consolidate devices into a single group for shared changes

If you need one change to reach many devices at once, move those devices under a single group and assign one Blueprint to that group.

1. Navigate to Devices & Groups and identify which devices need to share the same base configuration.
2. Move those devices into a single group so they share one Blueprint assignment. Devices in subgroups that have their own Blueprint assigned will not be affected by changes made to a parent group's Blueprint — only devices assigned directly to the parent group will receive the update.
3. Assign the updated Blueprint to the parent group under Devices & Groups → [Group Name] → Blueprint.

Verify: Navigate to Devices & Groups → [Group Name] → Blueprint and confirm the correct Blueprint is shown. Check that affected devices reflect the updated settings within 5 minutes. Devices in subgroups with their own Blueprint assigned should show no change.

If this doesn't resolve it

If a Blueprint appears to be applying settings unexpectedly, or you are seeing configuration on a device that does not match the Blueprint assigned to its group, contact Esper Support with the following information:

• The name and version of the Blueprint assigned to the affected group
• The device serial number or Esper device ID
• A screenshot of Devices & Groups → [Device Name] → Activity Feed showing recent Blueprint events
• A description of the setting that is not behaving as expected

Still need help?

If you're experiencing issues with managing cloned Blueprints as independent copies, submit a support ticket and include details about which Blueprints you cloned, what changes you attempted to make independently, and how the inheritance is affecting your device management workflow.