{"version":"2.1.242","anchor":"managed-settings-can-now-merge-across-sources-instead-of-the","canonical_anchor":"managed-settings-can-now-merge-across-sources-instead-of-the","heading":"Managed settings can now merge across sources instead of the top one winning","tier":"use","area":"Managed Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/managed-settings-can-now-merge-across-sources-instead-of-the","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Managed settings can now merge across sources instead of the top one winning\n\nAdmins can set managedSourcesBehavior to merge managed settings sources instead of only the top one.\n\n**What**\n\nA new enterprise settings key, `managedSourcesBehavior`, accepts `\"first-wins\"` (the default, and exactly today's behaviour) or `\"merge\"`. Under first-wins the highest-priority managed source present is the whole managed tier. Under merge, all present managed sources are deep-merged with fixed precedence and arrays unioned, so a lower source can contribute keys instead of being discarded. Any admin who sets the key gets it on this build; everyone else sees no change.\n\n**Details**\n\n- Managed source precedence is server-managed, then MDM \/ OS policy, then `managed-settings.json`.\n- Some keys never merge and are owned whole by the highest source present: `fallbackModel`, the restriction allowlists (`allowedMcpServers`, `availableModels`, `strictKnownMarketplaces`, `allowedChannelPlugins`) and the login pins (`forceLoginOrgUUID`, `forceLoginMethod`, `forceLoginGatewayUrl`).\n- The key is only honored when set in the highest-priority source, so a lower source cannot opt itself into merging.\n- Windows HKCU settings and `--managed-settings` never take part in the merge.\n- The key is stripped from the settings object before composition, so it never leaks into effective settings. It does not exist in 2.1.241.\n\n**Evidence**\n\n`managedSourcesBehavior`\n\n- Area: Managed Settings\n- Names: `managedSourcesBehavior`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5"}