{"version":"2.1.238","anchor":"per-feature-severity-thresholds-inert-without-server-config","canonical_anchor":"per-feature-severity-thresholds-inert-without-server-config","heading":"Per-feature severity thresholds, inert without server config","tier":"soon","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/per-feature-severity-thresholds-inert-without-server-config","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Per-feature severity thresholds, inert without server config\n\nSeverity thresholds can now be set per feature area from server config, and none are set.\n\n**What**\n\nSeverity thresholds can now be resolved per feature area, reading a `severityBySite` key from remote config that holds either the literal `\"on\"` or an object of thresholds, falling back to that area's own defaults. One area is wired up, keyed `handoff`. With no value from the server the result is a null threshold marked as coming from the default, so severity stays off unless remote config carries the key.\n\n**Details**\n\n- Two additional local conditions must also pass before the remote value is consulted.\n- In the same function the older bundle-based severity source is compiled out: the variable its `if` tests is assigned literal `null` immediately above, so that branch can never run. The per-model threshold map is the only remaining non-per-area route.\n\n**Evidence**\n\n`severityBySite`\n\n- Area: Permissions\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}