{"version":"2.1.238","anchor":"clearer-refusal-when-a-plugin-comes-from-unverified-managed-","canonical_anchor":"clearer-refusal-when-a-plugin-comes-from-unverified-managed-","heading":"Clearer refusal when a plugin comes from unverified managed settings","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/clearer-refusal-when-a-plugin-comes-from-unverified-managed-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Clearer refusal when a plugin comes from unverified managed settings\n\nPlugins from unverified managed settings now explain that you must approve the managed-settings dialog.\n\n**What**\n\nIf a plugin source was declared by remotely managed settings that this machine could not verify or that were never approved here, the refusal now says so and tells you to approve the managed-settings dialog once in an interactive session, or ask your admin.\n\n**Details**\n\n- The refusal is tagged `remote_policy_unconsented`.\n- Plugin server config entries now also record where each entry was declared, alongside its scope.\n\n**Evidence**\n\n`approve the managed-settings dialog once in an interactive session (or ask your admin)`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}