{"version":"2.1.269","anchor":"plugin-provided-config-settings-now-show-their-plugin-sourc","canonical_anchor":"plugin-provided-config-settings-now-show-their-plugin-sourc","heading":"Plugin-provided \/config settings now show their plugin source and can be locked by managed settings","tier":"notice","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/plugin-provided-config-settings-now-show-their-plugin-sourc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Plugin-provided \/config settings now show their plugin source and can be locked by managed settings\n\n\/config now shows which plugin a setting comes from, and organizations can lock those settings\n\n**What**\n\nWhen a setting in `\/config` was provided by a plugin (via that plugin's own configuration), the settings list now shows a small ` \u00b7 <plugin>` label next to it naming the source plugin.\n\nSuch plugin-provided settings can now also be locked, meaning a user can't change them, when they're set through an organization's managed settings or through a session's `--settings` option. Locking shows a specific message explaining which source locked the setting.\n\n**Why**\n\nThis makes it clear where a given setting is coming from when plugins are involved, and gives organizations a way to enforce plugin configuration choices that users can't override locally.\n\n- Area: Settings\n- Names: `\/config`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}