[FEATURE] disableBypassPermissionsMode should accept booleans (managed settings)
Resolved 💬 1 comment Opened May 29, 2026 by batmat Closed Jul 1, 2026
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
Two issues with the current naming:
- Double-negative naming: The field name already expresses the intent ("disable bypass-permissions mode"), so the value
"disable"reads redundantly/confusing. You expecttrue/false.
- confusing, because you may read it as "disable the disabling of bypass-permissions...", and bypass is also a negative to some extent 😅)
- No explicit opt-out: There's no way to set it to
false(allowed). You can only omit the field or set it to"disable". For managed settings, admins need to express intent explicitly.
Proposed Solution
Accept booleans, with the string "disable" grandfathered as equivalent to true:
// Current (confusing, only documented value)
"disableBypassPermissionsMode": "disable"
// Proposed
"disableBypassPermissionsMode": true // bypass mode is blocked
"disableBypassPermissionsMode": false // bypass mode explicitly allowed
// Grandfathered (still works, treated as true)
"disableBypassPermissionsMode": "disable"
Alternative Solutions
N/A
Priority
Low - Nice to have
Feature Category
Configuration and settings
Use Case Example
My company is setting up managed-settings file. Editing this file, and making sense of this field is unnecessarily hard 😅
Thanks!
Additional Context
_No response_
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗