{"version":"2.1.281","anchor":"managed-config-record-which-app-behaviour-keys-a-device-pro","canonical_anchor":"managed-config-record-which-app-behaviour-keys-a-device-pro","heading":"Managed-config: record which app-behaviour keys a device profile claims","tier":"internal","area":"Managed Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/managed-config-record-which-app-behaviour-keys-a-device-pro","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Managed-config: record which app-behaviour keys a device profile claims\n\nManaged settings now record which app-behaviour keys from a device profile are also set elsewhere\n\n**Unclear.** The finding does not say where the `groupClaimed` list is used or shown.\n\n**What**\n\nOrganisations can manage Claude Code through MDM, a system that pushes settings to company devices. When working out the final settings, Claude Code now also returns `groupClaimed`: the app-behaviour keys from the device profile that are also set locally or on the server. The existing warning that such keys are ignored is unchanged.\n\n**Why**\n\nThe keys that clash between a device profile and other sources are now collected in one list instead of only being warned about.\n\n- Area: Managed Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}