{"version":"2.1.238","anchor":"organization-consent-for-dangerous-settings-is-stored-server","canonical_anchor":"organization-consent-for-dangerous-settings-is-stored-server","heading":"Organization consent for dangerous settings is stored server-side when available","tier":"internal","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/organization-consent-for-dangerous-settings-is-stored-server","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Organization consent for dangerous settings is stored server-side when available\n\nYour consent to risky org-pushed settings is now stored on the server when one is available.\n\n**What**\n\nThe record of which risky organization-pushed settings you have consented to is now read and written through the remote storage client under the key `remote-settings-consent`, falling back to the local file when no remote store is present.\n\n**Details**\n\n- A record that cannot be read is now reported rather than silently treated as no consent at all.\n\n**Evidence**\n\n`remote-settings-consent`\n\n- Area: Settings\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}