I searched open and closed issues, pull requests, and discussions for comparable requests.
I believe this is appropriately scoped as a small feature request with an accompanying PR.
Problem Description
When Web Search is enabled, user prompts or generated web queries may be sent to the configured search provider. Some deployments need a user-facing reminder at the point of use, especially when Open WebUI is deployed in managed company environments.
For example, some managed deployments may need to make this processing boundary visible to users during privacy or compliance review without disabling Web Search entirely.
Proposed Solution
Add an optional Admin Web Search setting that shows a small warning in the chat input whenever Web Search is active for the current message.
The default should remain off to preserve existing behavior.
Alternatives Considered
Deployment documentation only: useful, but users may not see it at the point where they enable Web Search.
Always-on warning: too intrusive for personal/self-hosted deployments and would change existing behavior.
Provider-specific warning: less useful because the relevant boundary is Web Search itself and the deployment's configured search provider.
Additional Context
The warning is intended as a transparency aid, not as legal advice or a replacement for policy/consent flows. It is off by default so personal and self-hosted deployments keep the current behavior, while managed deployments can opt in.
Screenshots:
Originally created by @DuncanSARapp on GitHub (May 15, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24774
Related discussion: https://github.com/open-webui/open-webui/discussions/24772
## Pre-submission checks
- [x] I searched open and closed issues, pull requests, and discussions for comparable requests.
- [x] I believe this is appropriately scoped as a small feature request with an accompanying PR.
## Problem Description
When Web Search is enabled, user prompts or generated web queries may be sent to the configured search provider. Some deployments need a user-facing reminder at the point of use, especially when Open WebUI is deployed in managed company environments.
For example, some managed deployments may need to make this processing boundary visible to users during privacy or compliance review without disabling Web Search entirely.
## Proposed Solution
Add an optional Admin Web Search setting that shows a small warning in the chat input whenever Web Search is active for the current message.
The default should remain off to preserve existing behavior.
## Alternatives Considered
- Deployment documentation only: useful, but users may not see it at the point where they enable Web Search.
- Always-on warning: too intrusive for personal/self-hosted deployments and would change existing behavior.
- Provider-specific warning: less useful because the relevant boundary is Web Search itself and the deployment's configured search provider.
## Additional Context
The warning is intended as a transparency aid, not as legal advice or a replacement for policy/consent flows. It is off by default so personal and self-hosted deployments keep the current behavior, while managed deployments can opt in.
Screenshots:
@owui-terminator[bot] commented on GitHub (May 15, 2026):
🔍Related Issues Found
I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions:
🟣#21544feat: Add option to disable or restrict "Analytics/Analyse" dashboard for GDPR compliance This request is also about adding an optional admin-facing compliance/privacy control that changes the user experience only when enabled by an administrator. It’s not the same feature area, but it is closely related in intent: giving deployments a way to surface or restrict privacy-sensitive functionality. by sct-hm
🟣#24485 **feat: more control over web search settings; multiple configured search providers, and per-user settings. ** This feature request asks for more control over Web Search, including per-user policy and group access control. It is related because both issues concern admin-managed Web Search behavior and deployment policy around who can use search and under what conditions. by vanmilleru
🟣#20595issue: "search_web" tool executed even when "Web Search" control disabled This bug report concerns Web Search being used even when the UI control is disabled. It’s directly related to the new warning feature because both issues deal with the Web Search enable/disable boundary and what users should be aware of when search may send prompts externally. by SlavikCA · bug
🟣#20641issue: Web Search and Builtin Tools permissions break search This issue requests finer control over Web Search and Builtin Tools because search can leak information if it can’t be controlled separately. It is related to the new warning proposal since both are motivated by preventing unintended external search behavior in sensitive environments. by HenkieTenkie62 · bug, confirmed issue
💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead.
This comment was generated automatically. React with 👍 if helpful, 👎 if not.
<!-- gh-comment-id:4462589135 -->
@owui-terminator[bot] commented on GitHub (May 15, 2026):
<!-- terminator-bot:related-issues-reply -->
🔍 **Related Issues Found**
I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions:
1. 🟣 [#21544](https://github.com/open-webui/open-webui/issues/21544) **feat: Add option to disable or restrict "Analytics/Analyse" dashboard for GDPR compliance**
*This request is also about adding an optional admin-facing compliance/privacy control that changes the user experience only when enabled by an administrator. It’s not the same feature area, but it is closely related in intent: giving deployments a way to surface or restrict privacy-sensitive functionality.*
*by sct-hm*
2. 🟣 [#24485](https://github.com/open-webui/open-webui/issues/24485) **feat: more control over web search settings; multiple configured search providers, and per-user settings. **
*This feature request asks for more control over Web Search, including per-user policy and group access control. It is related because both issues concern admin-managed Web Search behavior and deployment policy around who can use search and under what conditions.*
*by vanmilleru*
3. 🟣 [#20595](https://github.com/open-webui/open-webui/issues/20595) **issue: "search_web" tool executed even when "Web Search" control disabled**
*This bug report concerns Web Search being used even when the UI control is disabled. It’s directly related to the new warning feature because both issues deal with the Web Search enable/disable boundary and what users should be aware of when search may send prompts externally.*
*by SlavikCA · `bug`*
4. 🟣 [#20641](https://github.com/open-webui/open-webui/issues/20641) **issue: Web Search and Builtin Tools permissions break search**
*This issue requests finer control over Web Search and Builtin Tools because search can leak information if it can’t be controlled separately. It is related to the new warning proposal since both are motivated by preventing unintended external search behavior in sensitive environments.*
*by HenkieTenkie62 · `bug`, `confirmed issue`*
---
💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead.
*This comment was generated automatically.* React with 👍 if helpful, 👎 if not.
<!-- gh-comment-id:4462610318 -->
@Classic298 commented on GitHub (May 15, 2026):
you opened this as issue AND discussion? Why?
closing - keeping dscussion open
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @DuncanSARapp on GitHub (May 15, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24774
Related discussion: https://github.com/open-webui/open-webui/discussions/24772
Pre-submission checks
Problem Description
When Web Search is enabled, user prompts or generated web queries may be sent to the configured search provider. Some deployments need a user-facing reminder at the point of use, especially when Open WebUI is deployed in managed company environments.
For example, some managed deployments may need to make this processing boundary visible to users during privacy or compliance review without disabling Web Search entirely.
Proposed Solution
Add an optional Admin Web Search setting that shows a small warning in the chat input whenever Web Search is active for the current message.
The default should remain off to preserve existing behavior.
Alternatives Considered
Additional Context
The warning is intended as a transparency aid, not as legal advice or a replacement for policy/consent flows. It is off by default so personal and self-hosted deployments keep the current behavior, while managed deployments can opt in.
Screenshots:
@owui-terminator[bot] commented on GitHub (May 15, 2026):
🔍 Related Issues Found
I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions:
🟣 #21544 feat: Add option to disable or restrict "Analytics/Analyse" dashboard for GDPR compliance
This request is also about adding an optional admin-facing compliance/privacy control that changes the user experience only when enabled by an administrator. It’s not the same feature area, but it is closely related in intent: giving deployments a way to surface or restrict privacy-sensitive functionality.
by sct-hm
🟣 #24485 **feat: more control over web search settings; multiple configured search providers, and per-user settings. **
This feature request asks for more control over Web Search, including per-user policy and group access control. It is related because both issues concern admin-managed Web Search behavior and deployment policy around who can use search and under what conditions.
by vanmilleru
🟣 #20595 issue: "search_web" tool executed even when "Web Search" control disabled
This bug report concerns Web Search being used even when the UI control is disabled. It’s directly related to the new warning feature because both issues deal with the Web Search enable/disable boundary and what users should be aware of when search may send prompts externally.
by SlavikCA ·
bug🟣 #20641 issue: Web Search and Builtin Tools permissions break search
This issue requests finer control over Web Search and Builtin Tools because search can leak information if it can’t be controlled separately. It is related to the new warning proposal since both are motivated by preventing unintended external search behavior in sensitive environments.
by HenkieTenkie62 ·
bug,confirmed issue💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead.
This comment was generated automatically. React with 👍 if helpful, 👎 if not.
@Classic298 commented on GitHub (May 15, 2026):
you opened this as issue AND discussion? Why?
closing - keeping dscussion open