Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ComplianceArea: what it touches
Internal ChangesKind: in v2.1.280,
Internal ChangesSection of the release
What
Several HIPAA-restriction entries (for example allow_account_plugins_sync) gained a serverPopulated: true marker. A helper treats a restriction as server-populated only when that marker is set and a remote kill-flag is not served true, which changes how compliance taints are merged when deciding whether an action is allowed.
The allow_cobalt_plinth policy entry (labeled "Artifacts", denied under hipaa/zdr) also gained serverPopulated: true, matching the pattern already used by allow_remote_control ("Remote Control").
Why
Marking these restrictions as server-populated lets them be controlled and killed remotely rather than being fixed at build time, giving more flexibility in how compliance policies are enforced for features like Artifacts.
