From 9b3d599c755a5ed7ba8a9cb14c4b66b5cedc05c0 Mon Sep 17 00:00:00 2001 From: Classic298 <27028174+Classic298@users.noreply.github.com> Date: Sat, 10 Oct 2026 18:09:31 +0200 Subject: [PATCH] fix: user can no longer chat after losing access to model controls they had used (#32194) A user who had picked an option in a model control (the per-model selector in the chat input, for example High on a Thinking control) could not chat any more once the admin switched off Allow Chat Controls or Allow Chat Params for them. Every message failed with "You cannot change model parameters.", and the user could not clear the saved selection because the selector is hidden for them. When either permission is off, the saved selection is now skipped when sending, so messages go through with the model's default options, and it applies again if the permission comes back. Fixes #31995 --- backend/open_webui/main.py | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/backend/open_webui/main.py b/backend/open_webui/main.py index 63f5fc6ccb..6cea135478 100644 --- a/backend/open_webui/main.py +++ b/backend/open_webui/main.py @@ -1202,7 +1202,8 @@ async def chat_completion( permissions = await Config.get('user.permissions') for permission in ('chat.controls', 'chat.params'): if not await has_permission(user.id, permission, permissions): - raise HTTPException(403, 'You cannot change model parameters.') + model_controls = {} + break if missing_base_model and model_controls.get(model_id): raise HTTPException(400, 'Model control options cannot be applied to the fallback model.') if model_info_params or request_params: