{"version":"2.1.257","anchor":"remote-control-settings-menu-now-shows-org-policy-lock-reaso","canonical_anchor":"remote-control-settings-menu-now-shows-org-policy-lock-reaso","heading":"\/config Remote Control setting shows org-policy lock reason","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/remote-control-settings-menu-now-shows-org-policy-lock-reaso","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### \/config Remote Control setting shows org-policy lock reason\n\nThe Remote Control toggle in \/config now shows as locked with a reason when your org policy disables it.\n\nThe \/config 'Enable Remote Control for all sessions' entry gained a locked variant: when `kKt()` (checking the managed setting `disableRemoteControl`) returns a reason, the setting is rendered as `type: \"managedEnum\"` with `lock: { reason, source: _q() ? \"managed\" : \"policy\", writableWhileLocked: [\"false\"] }` and a fixed value of `\"disabled\"`. The gate controlling whether the setting shows at all changed from a single `ch()` check to `_S() || _q()`.\n\nThe message 'Remote Control is disabled by your organization's policy (managed setting `disableRemoteControl`).' is now a shared constant reused by both the eligibility check and this new settings-panel lock logic, rather than being computed inline in two places.\n\n- Area: Remote Control\n- Names: `\/config`, `disableRemoteControl`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}