{"version":"2.1.224","anchor":"org-anchored-consent-for-remote-managed-settings","canonical_anchor":"org-anchored-consent-for-remote-managed-settings","heading":"Org-anchored consent for remote managed settings","tier":"notice","area":"Managed Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/org-anchored-consent-for-remote-managed-settings","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Org-anchored consent for remote managed settings\n\nApprovals for risky org-managed settings are now remembered per organization, so you get re-prompted far less.\n\n**What**\n\nWhen your organization ships managed settings, consent to the dangerous ones can now be recorded against the org rather than only against the local payload you saw. Consent is stored in a new `remote-settings-consent.json`, capped at 20 organizations and rewritten at most once a day per org, and you are not re-prompted while the org record's hash of the dangerous settings still matches.\n\n**Details**\n\n- Requests now carry the organization and account ids so the response can identify which org the consent belongs to.\n- Without an org record, the previous behaviour applies: the locally consented payload is compared directly.\n- Consent is not recorded if the signed-in identity changed part-way through the fetch.\n- A login or logout during a fetch discards that fetch's result, reported as `reset_during_fetch`.\n\n**Evidence**\n\n`Remote settings: Cache was reset (login\/logout) during this fetch; discarding its result`, `remote-settings-consent.json`\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}