Share a device baseline. Keep the differences deliberate.
A configuration brings together application assignments, launcher behavior, network settings, logs, and incident-reporting settings. Inherit a common baseline across related configurations, then override only the settings a product or site needs.
Map your configurations with usShare a baseline across device groups
A terminal baseline can hold application assignments, launcher release, log policy, and shared device settings.
- Store terminals: inherit the baseline and override supported network settings.
- Service terminals: inherit the baseline and override Background mode for another home launcher.
Parent changes reach settings that still inherit. Child overrides keep their own values; names, descriptions, and display colors remain local.
Know what inheritance changes
| Action | Result |
|---|---|
| Choose a parent | Settings without overrides and application assignments follow the parent. |
| Unlock a supported child field | The field becomes an editable child override. |
| Update a parent | Inheriting descendants receive the effective value and affected configuration versions update. |
| Override applications | The child owns the whole assignment collection. Applications are not merged package by package. |
| Switch parents | Existing overrides stay; other settings follow the new parent. |
| Remove the parent | The configuration keeps its current settings independently. |
Supported network, incident, and scheduled-reboot settings allow nested overrides. A configuration cannot inherit from itself or a descendant.
Choose what the configuration controls
- Applications: packages, versions, visibility, kiosk flags, and startup options.
- Launcher: release, Background mode, wallpaper, and kiosk system controls.
- Network: Wi-Fi, supported enterprise certificates, APN, proxy, SIM-lock policy, and data saving.
- Diagnostics: log severity, retention, uploads, and incident reporting.
- Maintenance: scheduled reboot, heartbeat interval, and configuration delivery.