{"version":"2.1.285","anchor":"managed-settings-helper-merge-doc-allowedproviders-is-a-w","canonical_anchor":"managed-settings-helper-merge-doc-allowedproviders-is-a-w","heading":"Managed settings docs: allowedProviders is replaced, not merged","tier":"notice","area":"Managed Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/managed-settings-helper-merge-doc-allowedproviders-is-a-w","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Managed settings docs: allowedProviders is replaced, not merged\n\nThe settings description now says allowedProviders, like the other restriction allowlists, is taken whole from the helper and not merged\n\n**What**\n\nOrganizations can supply managed settings (settings installed centrally by an administrator) through a helper program. The built-in description of how the helper's output is combined with other settings now lists `allowedProviders` among the restriction allowlists, alongside names such as `allowedMcpServers` and `availableModels`.\n\nWhen the helper provides one of these lists, that list is used as the complete value and is not merged with values from anywhere else.\n\n**Why**\n\nAdministrators who set `allowedProviders` through a helper can see that the helper's list is the whole list, so any provider missing from it is not allowed.\n\n- Area: Managed Settings\n- Names: `allowedProviders`, `allowedMcpServers`, `availableModels`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}