{"version":"2.1.232","anchor":"settings-rows-hide-when-the-value-is-set-outside-your-user-s","canonical_anchor":"settings-rows-hide-when-the-value-is-set-outside-your-user-s","heading":"Settings rows hide when the value is set outside your user settings","tier":"notice","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/settings-rows-hide-when-the-value-is-set-outside-your-user-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Settings rows hide when the value is set outside your user settings\n\nThe question auto-continue timeout row disappears when its value is set by policy rather than by you.\n\n**What**\n\nThe \"Question auto-continue timeout\" row is now hidden whenever its effective value comes from somewhere other than your own user settings, so a managed or policy-set value no longer appears as an editable field.\n\n**Details**\n\n- The row is consent-gated, and a failed save now restores the previous value in the panel rather than leaving the new one displayed.\n\n**Evidence**\n\n`Question auto-continue timeout`\n\n- Area: Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}