What
When 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.
Details
- Requests now carry the organization and account ids so the response can identify which org the consent belongs to.
- Without an org record, the previous behaviour applies: the locally consented payload is compared directly.
- Consent is not recorded if the signed-in identity changed part-way through the fetch.
- A login or logout during a fetch discards that fetch's result, reported as
reset_during_fetch.
Evidence
Remote settings: Cache was reset (login/logout) during this fetch; discarding its result, remote-settings-consent.json
Strings lifted out of the shipped bundle, so the claim above can be checked against them.