Skip to main content

Lock Configurations

Enforce settings across configurations using locks on the default configuration.

Written by Jeremy Bodokh

Overview

The Lock Configurations feature allows administrators to enforce specific settings from a default device configuration across all other configurations of the same type.

When a field is locked in the default configuration, its value is automatically propagated to all sibling configurations, and administrators cannot modify that field in non-default configurations.

Each device configuration type has a default configuration that acts as the reference for locked settings.

  1. An administrator edits the default configuration and toggles the lock icon next to a supported field

  2. Once a field is locked, its value is automatically copied to all existing sibling configurations of the same type

  3. Any new configuration created after locking will also inherit the locked value

  4. Administrators editing non-default configurations will see locked fields as read-only

Permissions

  • Any admin that can manage the default configuration (Admin or Delegated Admin) can change the lock status.

Locking a Field

Prerequisites: You must be an Admin editing the default configuration for the platform.

  1. Go to Devices > Configurations

  2. Select the default configuration for the desired platform

  3. Click Edit on the relevant tab (Global, Security, Applications, etc.)

  4. Look for the lock icon next to supported fields — an open lock means the field is currently unlocked

  5. Click the lock icon to toggle it to a closed lock

  6. Save the configuration

Once saved, the locked value is propagated to all sibling configurations of the same type.

Viewing Locked Fields

When editing a non-default configuration, locked fields appear as read-only text with a closed lock icon, indicating they are enforced by the default configuration. On the configuration detail page, locked fields display a closed lock icon on the right side of the field row.

On Files, Certificates and Applications deployment pages, locked assignments appear as grayed-out items with a "Locked" label and cannot be removed from non-default configurations.

Unlocking a Field

  1. Go to Devices > Configurations

  2. Select the default configuration for the desired platform

  3. Click Edit on the relevant tab

  4. Click the closed lock icon next to the field — it will toggle back to an open lock

  5. Save the configuration

Once unlocked, administrators can freely set different values for that field on each configuration.

Propagation Behavior

  • When a field is locked, the value from the default configuration is copied to all existing sibling configurations

  • For associations (apps, certificates, Wi-Fi, etc.), the item is added to sibling configurations if not already present

  • When a new configuration is created, all currently locked fields are automatically applied at creation time

  • When a locked association is removed from the default, the lock is cleaned up and the association is no longer enforced

FAQ

Can I lock fields on a non-default configuration?
No. Lock icons only appear when editing the default configuration.

What happens to existing values when I lock a field?
The existing values are overwritten with the value from the default configuration immediately after saving.

Does locking an application prevent it from being removed on the deployment page?
Yes. Locked applications cannot be deselected from non-default configurations. They appear grayed out with a "Locked" label.

I am a delegated admin. Why can't I change some fields?
Fields locked by an Admin appear as read-only on your configuration. Contact your Admin if you need a field unlocked.

Are locked values applied retroactively to devices?
Yes. When a locked value is propagated to a sibling configuration, devices using that configuration will receive the updated settings through the normal device sync process.

Did this answer your question?