Add quilr-web release notes for f3c76f854

docs/platform-areas/controls.md

@@ -54,5 +54,15 @@ Use Controls when you want to:
 
 ## Access Requirements
 
-Controls require Control permissions. Create, update, and delete actions depend on the user's
-assigned scopes.
+Controls require Control permissions. Available scopes and their effect:
+
+- **Create** — required to create a new control.
+- **Update** — required to edit an existing control or change its mode.
+- **Delete** — required to delete a control.
+- **Enable** — required to activate an inactive control using the toggle. Without this scope the
+  toggle is non-interactive on inactive controls.
+- **Disable** — required to deactivate an active control using the toggle. Without this scope the
+  toggle is non-interactive on active controls.
+
+Admins may hold any combination of scopes. Enable and Disable are evaluated independently based
+on the current state of each control.

docs/release-notes/index.md

@@ -8,6 +8,17 @@ hide_copy_dropdown: true
 
 # Release Notes
 
+## June 26, 2026
+
+### Fixed
+
+- [Controls](/platform-areas/controls): The enable and disable toggle on each control now enforces
+  separate Enable and Disable permission scopes. Admins who have only the Enable scope can activate
+  inactive controls; the toggle is grayed out on already-active controls for those users. Admins who
+  have only the Disable scope can deactivate active controls; the toggle is grayed out on inactive
+  controls for those users. Previously the toggle reflected only the general Update permission
+  regardless of whether the intended action was enabling or disabling.
+
 ## June 25, 2026
 
 ### Fixed